Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Remove duplicate columns for the projects having same release/fix version in 2D Statistics Gadget.

Edited

I have implemented versions globally (across the projects) using Version Synch plugin. Since, all the projects are sharing same version so it is expected that the tickets of all projects having common release/fix version should come in one column under 2D table at my Jira dashboard.  But, things are not going in that way still duplicate columns for version(s) appear in table.

1 comment

Comment

Log in or Sign up to comment
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 14, 2019

Each column in the gadget is a different version.  Versions are project objects, not global, so there is no such thing as a "common release/fix version" - every version in each project is a separate thing, and the gadget reflects that.

Like Ashutosh Dixit likes this

Thanks Nic for your comment.

 

Yes, I am aware about that (every version in each project is a separate thing, and the gadget reflects that). To overcome this limitation, I had used an add-on called 'Version Synch' with the help of this add-on, I am able to synch version (say Release 4.1.5) of one project (say X) with other projects (say A, B, C..etc.). That's the reason I used the word Global/Common.

Since, added version is proprietary of Project X so, if I rename version 'Release 4.1.5' to 'Release 4.1.5.0' under project X, new version 'Release 4.1.5.0' gets reflected to other projects A,B,C..

Can you please advise if there is any way to consolidate the data of duplicate columns (project specific) in one column?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 14, 2019

They are not "duplicate" columns.  Each version is separate and gets its own column, so each column is rightly representing one individual version.

  The add-on you've found synchronises between separate versions, not makes them the same thing (you'd have to rewrite a chunk of Jira to do that)

Can you please give me a hint how can I achieve it?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 14, 2019

Without rewriting Jira so that it has global versions, there's nothing I can suggest here.  Versions are done by project.  If you want a set of issues to use the same versions, they have to be in the same project.

Thanks for your response. 

I can not go by creating all tickets under one project as they correspond to different project module.

TAGS
AUG Leaders

Atlassian Community Events