I need to make some fields mandatory in bugs and stories as they are not being completed.
Hi @Jewels Truluck and welcome to the Community!
That depends. You can use the field configuration of your project to set certain fields as required. This is only a good idea if those fields can already be made required when your users are creating a bug or a story. Field configurations apply all the time to the work items in your project.
If a field only becomes required at some point in the lifecycle of your work item (e.g. you need to add a story point estimate to a story before development can start), then it may be better to add this to the workflow you use for those work items. In company managed projects, you would use a field required validator on the workflow transition where you want to make a field mandatory. In team managed projects, you would use a workflow rule to create a similar behaviour.
Hope this helps!
That makes a lot of sense. For our team its during the creation of story/bug that these fields are being omitted although they are available, so making them mandatory on creation is the key to ensuring we have the data we need to move forward.
I lost admin rights going to the cloud, so I need to get that established first then I can continue to improve our jira work items.
Thanks so much for you quick response :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.