Creates a screen and displays its fields in the task

[Eitan yomtovian]

Hello,

I created a new screen called 'On Hold' which appears as soon as the user moves the task to 'On Hold' status.
This screen has 2 new fields that I created, but there are some problems with them:
1. When I fill in these fields, they do not appear in the body of the task (I do not want them to appear when I create a task, but only as soon as I switch to 'On hold').
2. Once I define one of them as a required field, when I want to create a new task, the system forces me to fill this field as well (although I did not get 'On hold')

Regards,

Eitan.

[Fazila Ashraf]

Hi @Eitan yomtovian 

For the first problem, you will have to add those 2 new fields to the view screen of the issue type in the screen scheme.

For the second problem, making a field mandatory in field configuration scheme means it is mandatory in all the screens including create. For this use case you can use validators from JSU plugin. Refer https://confluence.atlassian.com/jirakb/how-to-make-jira-applications-fields-required-in-a-workflow-transition-691011903.html

[Eitan yomtovian]

Hi @Fazila Ashraf 

The second problem was solved with your advice with validation.

I did not understand your proposal to solve the first problem. Could you please elaborate more?

Thanks,

Eitan.

[Fazila Ashraf]

Hi @Eitan yomtovian 

Refer to https://confluence.atlassian.com/adminjiraserver/associating-a-screen-with-an-issue-operation-938847289.html for details about the screen scheme and the 'view issue' screen association.

There would be a screen associated to the view operations of the ticket. You will have to find it and add these 2 new custom fields in the view screens as well

[Eitan yomtovian]

@Fazila Ashraf 

Once I create a new task and fill in certain fields, once I set the screen ON HOLD as VIEW it displays only the data of the ON HOLD screen.
What do not I define correctly?

[Fazila Ashraf]

Hi @Eitan yomtovian 

That is the expected behaviour. Only the fields that are in the screen you are associating for view operations will be visible when the ticket is viewed.

Create a new screen with all the fields of the project in it. And set that as the view operation screen