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

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
4,556,392
Community Members
 
Community Events
184
Community Groups

Grouping quick transformations

Is there a way to create custom sets of quick transformations? I have a structure that has a number of quick transformations for different use cases. E.g. for a roadmap I want to group quick transformations A, G, U. For a PI planning view I want to group A, B and K. It seems that A can only belong to one group, so it seems that I cannot create sets of transformations for different use cases. Am I correct in my observation or is there a way to allow one Quick transformation to be part of more than one transformation group?

1 answer

0 votes
David Niro _Tempo_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 17, 2023

Hi @Matti Larborn !

You're correct that once you add a transformation to a Group, it is no longer available to be added to a different group.

That being said, you can create the transformation again and add it to the other group.

Hope this helps!

Best,
David

It would have been great if the groups would be sets instead, then I did not have to have duplicates of the transformations, but I have seen that this could be an option. Having multiple instances of the transitions in different groups makes the maintenance of those transformations more time consuming and error prone, as I need to change all of them and not forget any single of them. That is why sets of transformations would have been better.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events