I have a screen where developer enters specifications and submits for review. Reviewer can return or accept the specs. In case specs are rejected, reviewer enters comments and returns. Developer has to then read the comments, modify the specs and resubmit. In the custom screen used for entering specs and review comments, I have created a field where the reviewer has to mandatorily enter review comments.
But the problem is that the same screen is used to enter spces. Due to this, system checks for mandatory condition even when developer wants to submit the specs first time. Ideally, I would want the following:
Is this possible?
The first part of your question is simpler, you can set a field as mandatory depending on status, using a transition condition in workflow.
But making it read only is more complex, I think you could validate via transition condition too, that Developer not change its value, but I don´t know how to not allow to edit it...
One option to make a field read-only is to create different "edit" and "view" versions of your issue screen and associate them with the Edit issue and View Issue operations, making sure the read-only field is not on the "edit" screen.
To allow the 'read-only' field to be set at the right point in the workflow, put the field on another custom screen and associate the screen with the relevant workflow transition. As Aylin says, you can make it mandatory using a transition condition in the workflow.
First of all, many thanks to both of you for answering so quickly!
I was able to follow the suggestion by Aylin (and Sam) to set the 'mandatory' property to the field as required.
But Sam, the approach to make the field read-only seems to be quite convoluted - isn't there something more simple?
There's nothing more simple that I know of I'm afraid, and it's not too hard if you get your screens set up right. It's basically the solution described here.
For your scenario you would need something like:
This assumes you are OK with the 'specifications' and 'review comments' fields only being visible on the issue view screen.
i.e. the developer will see the 'review comments' and 'specifications' fields when viewing an issue. They will only be able to edit the 'specifications' field by clicking 'submit for review'. The 'review comments' field won't show while they are doing this (otherwise they'd be able to edit it too!).
If you really want read-only fields to be displayed during the transition, the above won't achieve it.
Your other options could be:
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs