-
Suggestion
-
Resolution: Won't Fix
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
We can add custom fields to an issue. Would liek to be able to ad custom field to a comment. This would allow a catagory type drop down when adding a comment.
- is incorporated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
[JRACLOUD-1542] Custom Fields on Comments
Jan Carlin
added a comment - This would make my day as well. I'd like to have comments that are of a specific type: "executive summary" (a consice summary of the current understanding of the issue while in progress), "knowledge-base digest" (the essence of the issue which would be made into a knowledge base entry by an automated process after the issue is closed), "escalation justification", "hand-off info" (daily statuses for handoffs).
What I do now is to create sub tasks but that is a "heavy weight" kind of solution to a kind of simple problem.
Comments are also the only "native" one-to-many format in JIRA so I can see wanting to have a comment be of types "customer technical contact" (if there are more than one for this issue, maybe one for each 12 hour period), "broken component combination" and "working comp comb" (for third party components that have been tested by the reporter while using our product) and more I am sure.
Jan Carlin
added a comment - This would make my day as well. I'd like to have comments that are of a specific type: "executive summary" (a consice summary of the current understanding of the issue while in progress), "knowledge-base digest" (the essence of the issue which would be made into a knowledge base entry by an automated process after the issue is closed), "escalation justification", "hand-off info" (daily statuses for handoffs).
What I do now is to create sub tasks but that is a "heavy weight" kind of solution to a kind of simple problem.
Comments are also the only "native" one-to-many format in JIRA so I can see wanting to have a comment be of types "customer technical contact" (if there are more than one for this issue, maybe one for each 12 hour period), "broken component combination" and "working comp comb" (for third party components that have been tested by the reporter while using our product) and more I am sure. 
Owen Fellows
added a comment - I am not sure why this si needed. Whould you be able to give more details about why you would like this.
Owen Fellows
added a comment - I am not sure why this si needed. Whould you be able to give more details about why you would like this. 
Hi,
This is a bulk update to specific issues in the JIRA (JRA) project
As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.
Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com
If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.
Best regards
Josh Devenny and Roy Krishna
JIRA Product Management