Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,551,871
Community Members
 
Community Events
184
Community Groups

Using an insident template

Kristian Magnus Lingsom
Kristian Magnus Lingsom Mar 31, 2023

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? 

Answer
Watch
Like Be the first to like this
146 views

1 answer

1 accepted

0 votes
Answer accepted
Mubeen Mohammed
Mubeen Mohammed
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 03, 2023

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.

Regards

Mohammed Mubeen

Cloud Support Engineer

Reply

Suggest an answer

Log in or Sign up to answer
Statuspage
Statuspage
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events

See all events