-
Suggestion
-
Resolution: Duplicate
-
None
-
3
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
In a similar function to Confluence, customers would like to be able to add comments to attached files on a JIRA Issue
Suggested Solution
Incorporate an option where Users can include comments directly on Attachments in JIRA
Workaround
Comments about the attachment can be added on the JIRA Issue
- duplicates
-
- Closed
- is duplicated by
-
- Gathering Interest
- is related to
-
- Closed
[JRACLOUD-61395] Comment on Attached File in JIRA
I believe this issue is a duplicate of JRACLOUD-38871 – New HTML5 image attachment lacks possibility for comment
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!
Commenting in development work flow is a "micro-task" that has a very large positive impact on productivity.
> It is a foundational tool for promoting "connectedness" in teams, which is critical to people feeling safe and being willing to contribute.
> Any single comment can potentially be very valuable, in terms of reducing risk, increasing utility or identifying shorter development paths, so any resistance to commenting has a large overall opportunity cost.
So anything that makes commenting better is going to be very valuable for development productivity.
This is not a knock on the suggested workaround, however, there is a very big difference in usability and communication at the micro-task level between commenting directly on embedded documents (as in Confluence), and commenting in the issue on an attachment (as in the suggested workaround).
Think about (with the workaround)
- many, many people
- taking several extra steps to add comments,
- having to add context to the comments,
- having to use lots and lots of short term memory to connect the attachment to the comment in the issue,
- experiencing many, many of events of losing focus connecting the comment to the document, and
- many, many ideas being lost because of people not bothering with the comments because of the extra work
Compared to:
- many, many people with very little effort being able to directly see the connection between comments and the document, instantly understanding the context of the comment, being inspired by comments made by other people, and easily adding their own ideas as quickly as they occur, directly in the middle of the development process, using rich format documents instead of just plain text pages.
Please give this one a high priority. You've got the technology in Confluence. It just needs to be ported over ( smiley on the "just").
Jim Johnson
added a comment - - edited Commenting in development work flow is a "micro-task" that has a very large positive impact on productivity.
> It is a foundational tool for promoting "connectedness" in teams, which is critical to people feeling safe and being willing to contribute.
> Any single comment can potentially be very valuable, in terms of reducing risk, increasing utility or identifying shorter development paths, so any resistance to commenting has a large overall opportunity cost.
So anything that makes commenting better is going to be very valuable for development productivity.
This is not a knock on the suggested workaround, however, there is a very big difference in usability and communication at the micro-task level between commenting directly on embedded documents (as in Confluence), and commenting in the issue on an attachment (as in the suggested workaround).
Think about (with the workaround)
many, many people
taking several extra steps to add comments,
having to add context to the comments,
having to use lots and lots of short term memory to connect the attachment to the comment in the issue,
experiencing many, many of events of losing focus connecting the comment to the document, and
many, many ideas being lost because of people not bothering with the comments because of the extra work
Compared to:
many, many people with very little effort being able to directly see the connection between comments and the document, instantly understanding the context of the comment, being inspired by comments made by other people, and easily adding their own ideas as quickly as they occur, directly in the middle of the development process, using rich format documents instead of just plain text pages.
Please give this one a high priority. You've got the technology in Confluence. It just needs to be ported over ( smiley on the "just").
As per this comment I am closing this ticket.
If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it as needed.