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,457,715
Community Members
 
Community Events
176
Community Groups

Identify the required fields on issue creation

I'm creating a dynamic process that needs to know the required fields on creation from a specific project and issue type. 

In my understanding, they could be defined in 3 places:

  • Field Config 
  • Workflow initial screen 
  • Script runner behaviors 

I'm willing to let go the behaviors ones since it could be a bit more complex.

After some time researching, I don't get too much luck. The nears thing that I found is the QuickCreateIssue endpoint that returns a json that identify if a field is required. But even that, I don't know how to request it. 

 

Could anyone provide some help on archiving this? 

1 answer

1 vote

Not quite.  Your list should be:

Field Config

Workflow validator on the create transition

SR Behaviours

But there are problems with them - the REST API won't tell you about the validators or the Behaviours.  The only way to work those out would be to read the workflow and parse it for the use of a validator (which could be hard as there are many validators out there, even Scripted ones meaning that you'd have to read the scripts behind them too), and read all the Behaviours set up in SR to work out if they make fields mandatory.  On the bright side, most people don't use validators to make fields mandatory on create, because field configs do it.

The field config is a bit of a faff to get your head around, you have to read the project and issue type to find the field config in use, then you can ask that what fields are mandatory, but it is plain and simple to do.

This is the sort of question that makes me ask "Why?".  What are you trying to achieve here?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events