My company supports a variety of different brands and products. We currently have "Brand" as a required field on all tickets in JIRA. I find this to be cumbersome as it requires developers to select this brand anytime a ticket is created. Is there a more nuanced way to solve this?
I was thinking we could apply that field to higher level issues like Epics or Initiatives. If the brand field is selected on EPIC, then we an assume all children issues are associated with that brand.
Thoughts?
Perhaps you can use the 'Swimlanes' feature in the Board settings.
You could create a swimlane (based on queries) for each Brand, and then when a ticket is created it is automatically placed in the backlog until someone drags it into a brand/swimlane?
Might still be cumbersome depending on the workflow, but the responsibility this way would be on just 1 person rather than any individual person.
I'm still quite new with Jira so this may not work as I imagine, but food for thought!
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.