Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Manage bugs which affect multiple project releases

Deleted user Oct 31, 2019

Hi all.

I could really use your advice here.
I'm new to Jira and trying to find a solution to this challenge.


- Project has multiple releases;
- A release corresponds to a stand-alone, long-term supported product;


- A bug can affect multiple project releases;
- For different project releases, there could be different bug owners, issue progress, issue resolution;
- Must see bug status/progress over all releases (eg: in a nice table);
- The sweet point between user friendliness and setup easiness would be that I don't need custom-written plugins unless impossible otherwise;

My solution through an example

Take several releases: 1.0, 1.1, 2.0.

Bug creation

Have a separate issue for each release.

A bug is found in version 1.1.
Create a Bug issue (eg: TheScaryBug) for version 1.1.
Seems it affects versions 1.0 and 2.0 as well.
Clone TheScaryBug for 1.0 and then for 2.0.

This way, all bugs will actually have the same summary.

Aggregated bug view

To see bug status over all releases, I thought of Structure:
- have a structure dedicated for bugs;
- have a Generator which imports all bugs;
- have a Generator which groups by Summary (all issues having same summary fits now);
- add "Affected Versions" & "Status" columns;


Grouping by Summary in Structure doesn't seems possible.
I tried to select Summary field for grouping but couldn't find it.
I created another column which takes value from either "Summary" field or custom formula pointing to summary field. Seems Grouping doesn't care about actual structure columns.


Q1: How can I group by Structure items by summary?

Q2: How would you handle this challenge?

Thank you for your time and input.


Deleted user Oct 31, 2019

This should better stay in Questions, not Discussions.

Could an admin move it?


Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 07, 2020


To group by any text field, you should select "Group by" - Text Attribute and then select Summary in the drop-down of attributes.

Kind regards,


[ALM Works]


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events