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: 

create required field for resolition screen only

Sebastien Gadbois
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 14, 2013

I try to use a new field for the resolution screen, but if i make required this field i can't create new bug without this one.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
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.
March 14, 2013

Fields in Jira are either required or not. For the entire life-cycle of an issue. (This is a known weakness in Jira, but it's not obvious at first). You control that with field configurations.

Screens are pretty much irrelevant here, all they do is say "show these fields to users if they're on this screen".

The work-around is to use "validators" on the workflow, so that a user trying to leave your field blank when going between status is thrown back to the screen with a "this field is mandatory" type message. There are no validators like this built into Jira, but many highly recommended plugins all provide them (Jira suite utilities, jira misc workflow extensions, etc)

TAGS
AUG Leaders

Atlassian Community Events