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,297,846
Community Members
 
Community Events
165
Community Groups

I don't want issues to be create without epic link, sprint and original estimate as required fields

I want epic link, original estimate and sprint as required fields while I create any issue in Jira

2 answers

0 votes
Mykenna Cepek Community Leader Apr 26, 2022

Another approach is to use a Workflow Validator. I think they can be used for new issues, before they transition to the first state in the workflow.

On that transition in the workflow, put a set of "Field required" validators, one for each field.

I believe it also allows you to include an error message for the user when the validation is not met. In a case like this, I'd suggest a message like "The Epic Link, Sprint and Original Estimate fields are required".

The decision to use field configuration or workflow validation might be influenced by which of those are shared across multiple projects, and whether this limitation applies to them all.

0 votes
Alex Koxaras Community Leader Apr 26, 2022

Hi @Saad Tanveer 

Make them required within the field configuration of any issue type. Make sure to include them in the create screen of all issue types. Keep in mind that subtasks do not have epic link.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you