Require a field during specific transitions
Asked by Kim Killen:

This is the part of Jira I just cannot wrap my head around! I'm pretty sure it's because Jira named items by simply reordering the same four or five words and then added "scheme" at the end...? Or is it just me?

Here's what I need help with A team would like to require the 'Time Spent' field when the following transitions take place:

* When the status of issue type Mobile Setup goes from Pre-Alpha to Alpha
* When the status of issue type Mobile Setup goes from Pre-Beta to Beta
* When the status of issue type Mobile Setup goes from Pre-Submit to Submit
* When the status of issue type Mobile Resubmit goes from Pre-Submit to Submit
* When the status of issue type Mobile Task goes from In Progress to Resolved
* When the status of issue type Hotfix goes from In Progress to Done

Here is a list of the schemes, etc. from the Project Summary:

* Issue Type Scheme: Default Issue Type Scheme (migrated)
* Workflow Scheme: MYS Workflow V4
* Screen: Default Screen Scheme (migrated)
* Scheme: Default Issue Type Screen Scheme (migrated)
* Fields: Default Field Configuration (migrated)
* Scheme: Default Field Configuration Scheme

![Configure Screen Scheme.png](/t5/image/serverpage/image-id/337429i703DE0787E839D3E/image-size/large?v=v2&px=999 "Configure Screen Scheme.png")![Field Scheme.png](/t5/image/serverpage/image-id/337427i9DF388DFC1FC697C/image-size/large?v=v2&px=999 "Field Scheme.png")![Issue Configure Screen.png](/t5/image/serverpage/image-id/337428i1BF0F7CB1EB9A51C/image-size/large?v=v2&px=999 "Issue Configure Screen.png")![Issue Type Scheme.png](/t5/image/serverpage/image-id/337430iF398D5E0BCCE5772/image-size/large?v=v2&px=999 "Issue Type Scheme.png")![Screen Scheme.png](/t5/image/serverpage/image-id/337431i14227540F0C94227/image-size/large?v=v2&px=999 "Screen Scheme.png")![Workflow.png](/t5/image/serverpage/image-id/337432i14D933C2F571F022/image-size/large?v=v2&px=999 "Workflow.png")

How do I go about doing this?

I confirmed, *I believe*, that the Time Spent field is configured to be visible on the Configure Screen Scheme.

And don't be stingy here. Act as if you are talking to a 9-year-old. Pretty please with a cherry on top!


Answers:
author: ?ukasz Modzelewski _TTPSC_
body: Oh yes, it is twisted and can easily confuse, then finding things in navigation can be like a lottery! Also some time button edit edits something, and sometimes it triggers name change...  

My first advice would be to separate settings for 1 out of 2307 projects for a test, just in case you mess up :D

If you want to add/update some data manually on transition, you will need to add some screen (the modal where user can update data), on that screen you can list and mark required fields you need and your user need to fill.

You can do that in screens section. Same screen can be used on different occasions so make sure you describe the intent or make it crystal clear what it should cover.  
eg.  
![xray example.png](https://community.atlassian.com/t5/image/serverpage/image-id/337435i7BA4863FB6A4C78C/image-size/large?v=v2&px=999 "xray example.png")

Then in given workflow, on given transition you need to hit the edit button and add the created screen :)   
![rejected.png](https://community.atlassian.com/t5/image/serverpage/image-id/337436i48256B83CD79B489/image-size/large?v=v2&px=999 "rejected.png")

This way, when user performs this transition, chosen screen will show in modal prompting user to fill required fields.

You should check some of the free university trainings for workflows eg. <https://university.atlassian.com/student/catalog/list?search=workflows>


author: Shawn Doyle - ReleaseTEAM
body: Multiple ways to achieve this. I do applaud you for making sure the field is visible in all screens before making it mandatory.

I would lean toward a workflow condition or validator. Go into the workflow(s) in question, and add the condition to make that field mandatory.

comments: author: Kim Killen
body: Thanks, Shawn. Do I need to be concerned with specifying an issue type? For example, "issue type Mobile Setup goes from Pre-Submit to Submit". I only want the Time Spent field to be required IF the issue type is Mobile Setup AND the status is transitioning from Pre-Submit to Submit.

Do I need a condition?

Is the validator in the screenshot correct?

![Validator.png](https://community.atlassian.com/t5/image/serverpage/image-id/337699i9C639F8CEF6A859B/image-size/large?v=v2&px=999 "Validator.png")


author: Shawn Doyle - ReleaseTEAM
body: yes, you do need to look at which issues types are using this workflow. As [@?ukasz Modzelewski _TTPSC_](/t5/user/viewprofilepage/user-id/1144009) points out, it is best to make a copy of this workflow and the different schemes to isolate the changes to just the projects and issue types you would like the changes to apply to.


author: Kim Killen
body: Now I come across this error message...![Screenshot 2024-08-13 103458.png](https://community.atlassian.com/t5/image/serverpage/image-id/341530i51F06EC3ED4855B9/image-size/large?v=v2&px=999 "Screenshot 2024-08-13 103458.png")

Don't forget - speak to me as if you're teaching an 8th grader.

Help me, I'm poor.

![](https://i.giphy.com/media/v1.Y2lkPTc5MGI3NjExMGI4MTJrbmtmN3h5czgybmNrdHNmMncwb2V3MnM4cHA4cGZjaGNuZCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/Mzeny7G8pCmCk/giphy.gif)


Tags: cloud

jira-cloud