Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Making a field required for only one Issue type?

Sarah Shonnard
Sarah Shonnard November 14, 2012

Is it possible to make a field "Required" for only one Issue type?

We're using Greenhopper and have three top level issue types: Epic, Story & Bug.

I'd like to make the "Affects Version/s" field mandatory for only the Bug issue type.

Answer
Watch
Like Tania likes this
928 views

2 answers

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
November 14, 2012

Field configuration scheme.

This lets you say "field config 1 for issue type A, field config 2 for issue type B, and field config 3 for the rest"

Reply
0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
November 14, 2012

Field configuration scheme.

This lets you say "field config 1 for issue type A, field config 2 for issue type B, and field config 3 for the rest"

Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira Software
TAGS
AUG Leaders

Atlassian Community Events

    See all events