Hi community
Currently running Jira v9.4.17
Id like to create a comments/running note field accessed by every Jira ticket which shows the same comments in every ticket - so its not a comment field specifically for that ticket/client or product.
Its a field that my team can update from any ticket they are on.
Not sure if Im making sense?
Paul
Hello @Paul Mosca
Can you tell us more about the use case for this, and the problem you are trying to solve?
My team currently captures & stores certain information in an excel sheet.
The sheet has a comments field staff update on a daily basis, like a diary, so you can read the entire history in that field, like sticky notes.
I want to replicate this within Jira & want to create, if possible, one comments field accessible from any Jira ticket where staff can continue updating in a rolling update process.
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not aware of a way to do that.
There might be work arounds available, like storing the data elsewhere and having a way to have a custom field pull the data in from that external source. Or having a custom field where updates to it in one issue are propagated to the same field in all the other issues.
I'm not really clear on what problem/requirement is addressed by having a that sort of shared content across all issues. Can you elaborate on the type of content the field would have and how it would be useful to have that content available and updatable from any issue? I am curious to understand more about your use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What Im trying to achieve is to have a common field within all tickets that has the same info regardless of the ticket an agent is in, so when they update a particular set of details for a client, they will be able to see or update in that universal comments field, the latest items we need to be aware of, year to year, regarding complex decisions or complex Architecture, product name changes etc...
This is what I propose to do away with using excel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think Jira is the right solution for your problem. Jira is, in my experience, work item focused. I have not heard of any use case similar to yours. It is quite possible that I am missing details of your use case or business model that would help me understand the problem you're trying to solve, and why you think it should be solved in Jira.
There are collaboration tools, like Confluence, that I think would be better suited for hosting a single source of truth accessible to and updatable by many people.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.