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,555,149
Community Members
 
Community Events
184
Community Groups

Hey! how to make a field mandatory in the resolve issue screen? (not in create /view/edit ).

i want to make a field "x" mandatory in the resolve screen. i dont want to use field validator in workflow. is there any other workaround to do that?

1 answer

1 accepted

0 votes
Answer accepted
Florian Bonniec
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 09, 2023

Hi @kp troopr 

You will need to use a validator in the WF, if you want to set a customfield required it will require an app such as Jira Suite Utilities or Scriptrunner or another one available on the marketplace.

Using scriptrunner you can use behaviour to set field require during a transition but it only set it required when the user is using JIRA UI not REST API for instance.

Regards

Thanks for response @Florian Bonniec . cant i do without it?

problem is - whenever i want to make  my field "required" in a specific screen (resolve screen) then its becoming required in create screen also.

Radek Dostál
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 Leaders.
May 09, 2023

Workflows are based on transitions - you're setting a mandatory field for a specific transition and that transition only.

If you're seeing a mandatory field on Create, then it has nothing to do with your resolve screen, that's something else you're doing.

As a hint - resolution is always mandatory wherever you add it. So if that's your field, don't add it to project screens, only add it to the transition screen (must be a different screen than the one you use for create/edit/view). I think you might not even need a validator for it in that case.

Florian Bonniec
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 09, 2023

@kp troopr , you can use behaviour included in Scriptrunner to do that but it will only apply via the UI not REST API.

I do not see any other way to do it.

Regards

i am making a field required (named "complexity") from, project settings > fields > and then making it  required . this field is not addd in the view/edit /create screen . only it added in workflow resolve screen .but

  • always whenever  i create issue it doesn't show up in issue create form but shows pop-up message in jira that "field is required". 
  • or if i create request form portal than it shows that field. and i cant remove that. so is there a way to not show as well as in  request portal form. and how can i make this field required only in wflow resolve screen. -->
  • image.png
Florian Bonniec
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 09, 2023

Yes it's why you need an app, you cannot use Field configuration for that because it apply to the issue at any state of the life cycle of the issue. If you want to do it at some transition you need a validator or a behaviour (using scriptrunner).

Like kp troopr likes this
Radek Dostál
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 Leaders.
May 10, 2023

Ok great so at some point you figured "hey fields > find field > make required", "oh yeah this definitely means the resolve screen and nothing else". I mean, you could just apply common sense or google to first 3 pages to realize that's not how to you make a field mandatory for a transition.

https://letmegooglethat.com/?q=jira+make+field+mandatory+on+transition

 - first link even says in preview what field configuration does

 - second link is the exact kba you're asking about

 - third link is the same post, even though it's tagged as cloud it applies just the same

Like kp troopr likes this

Suggest an answer

Log in or Sign up to answer