The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

how to identify a type of problem

Victor Tobon
July 19, 2021

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Iago Docando
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 20, 2021

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.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events