For several of our clients, we ask them to raise support queries in the JIRA backlog & prioritise them in the "To Do" column of our Kanban board. This means that if they want us to assist with a specific Support Query, they define whether it is a higher priority than the work in progress or next story.
When we then do a release, if we want to close the issue from the backlog, we need to assign a release even though it's often not a code based solution. Does anyone have any suggestions for managing this better?
We use the JIRA FixVersion field for non-code-related tasks. This helps us to identify all work which was done (even if non-code related) during the time the release was being developed.
If you don't want non-code-related tasks to be included in specific release (JIRA FixVersion), you could invent a 'special FixVersion' (e.g. 'Support_Query') and assign all the support query issues to that value.
Hello all! It has been 20 years since the agile manifesto was introduced, and closer to 40 years since software development began moving away from a waterfall-type approach. While many teams have ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events