You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
This question is in reference to Atlassian Documentation: Using JIRA for Change Management
I would like to group a series of issues (e.g. change requests) into a bundle or work order so that they can be assigned to a user for execution. The ordering of execution within the group is important. As is the order of execution of different groups. I already have the concept of a standard-issue type of 'Change Request'. Must I change to a Epic/issue/sub-task model to achieve this?
Not necessarily - you could use a custom field to do it as well - queries for "custom field = x" would then give you the grouping. A labels type field might be the most appropriate, if you want to let your users define the grouping for you.
Thanks Nic. That is an option. I'm hoping to make this process as lightweight as possible for the admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.