You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
is it by design or is it a bug that if one start to create an incident from template 1 where component A is selected, and then select template 2 where component B is selected that the incident when published list both component A and component B as affected?
Hello @Kristian Magnus Lingsom
Thank you for contacting the Atlassian community! this is Mubeen.
The component's selection as affected when switching from one template to another is not the expected behavior. We have opened a bug request with our engineering team to further investigate this, STATUS-569 is the ticket ID for your reference. Thank you for notifying us of this issue, If you wish to get further updates on the bug request raised you can directly contact our support team at https://support.atlassian.com/contact/ and refer to the ticket ID STATUS-569.
I hope the information provided is helpful.
Cloud Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.