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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can i change the color of versions so they are uniq instead of all the same Edited

In the backlog view, stories show up w/ two small colored box, one for the epic the story is under and the other for the version (a.k.a. "Fix Version/s") that the story is in. 

I know how to change the color for epics.  You click "epics" in the backlog view, then click on the ... next to the epic and it pulls up the color palette to change the color. 

But I can't seem to change the color of versions.  Instead they are all grey.  And doing the above, when clicking the ..., I only get "edit name".  Having different/uniq colors for the version is very valuable just like for the epic colors.

I also tried at the "releases" page where versions are created but dont see it there either..

 

 

 

 

1 answer

0 votes
Sudarshan TS Community Leader Dec 04, 2020

Hi @MC 
What is the value of seeing colored versions?

My Understanding is for Epics there are assorted colors because a sprint may have stories from different epic, hence for the differentiation a color is given.

Same reasoning.  We have parallel efforts going on.  So working not only different epics in the same sprint, but different versions.  So color differentiation would be very useful.

Sudarshan TS Community Leader Dec 06, 2020

Good.!
But, the idea of a Sprint is to have a valuable and usable version.! (one perfect release in the end, one Ship)
If you have multiple versions in a sprint, you may not realize potential of scrum for a good delivery.

I suggest trying the below if it is possible at your end:
1. try to have your sprint backlog with the same version (even if its from different epics they should belong to one connected Release version number)
2. if you are having multiple versions in a sprint, it means you are working on different independent products (in that case your team must decide why scrum?)
(like a 5-member team working on 2 or 3 applications)

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you