Modify ticket creation workflow such that new bugs or user-story can't be created without specifying Epic in the epic field
Are you working with Jira Cloud or Jira Server/Data Center?
If Cloud, are you working with a Company Managed project or a Team Managed project?
If you are working with Jira Server/Data Center, or work with a Company Managed project in Jira Cloud you have two choices:
1. Create a Field Configuration where the Epic Link field is set to Required. In the Field Configuration Scheme for your project, set that Field Configuration to be associated to the Bug and User Story issue types. This will require the Epic Link be filled in always for those issue types.
2. If you don't have Workflow(s) that are already specific to the Bug and User Story issue types, create them by copying the workflows that those issue type currently use in your project. The modify the new workflow(s) in the Create transition. Add a Validator on that transition and use the Field Required Validator option to specify that the Epic Link field is required. Add the new workflow(s) to the Workflow Scheme used by the project, and associate the new workflow(s) to the two issue types.
Note that if your Field Configuration Scheme or your Workflow Scheme is shared with other projects, those other projects will be affected by this change. If you need to affect only one project, you may also need to create a new Field Configuration Scheme or a new Workflow Scheme that can be associated with that one project so that others will not be impacted.
I'm working with Jira cloudÂ
Are you working with a Company Managed project or a Team Managed project?
Do you have more question based on the information I provided?
I'm working with company managed project jira cloud.
The Epic link is locked ,can it be unlocked so that I can modify tickets such that user story/bug cannot be created with Epic link.
Field configuration is Default , is it because of this Epic link is locked ?
It looks like you're new here. Sign in or register to get started.
