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,462,992
Community Members
 
Community Events
176
Community Groups

how to identify a type of problem

Good evening jira community, I would like to know if anyone has an idea of ​​how to identify a specific type of issue, for example a user story and in case it is not this type of issue, do not allow the creation of it or if it is linked the incident in case of not being a user story that the request is eliminated.

1 answer

1 vote

Those are two different things:

1 - Allowing ONLY the creation of a number of predefined issuetypes is easily achieved just by setting up a correct issuertype schema for your project. Nothing fancy about it, just basic project management.

2 - If <something happens> then <automatically do something> is nothing but an automation. You should check some plugin / app (automation for jira, scriptrunner...) and give it a try so you can see what's available to you.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events