group change requests

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?

1 answer

0 vote

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.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

272 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you