Affects Version/s: 5.4.7
Fix Version/s: 5.4.11
When a behaviour is added to a field to make it read-only on everything except the Create screen, then you attempt to create an issue where this behaviour should be applied on top of another issue where that field is read-only and fail validation on the first create attempt, the field will be mistakenly made read-only. This only happens if the behaviour is applied alongside a second behaviour that makes an additional field required (see steps to reproduce and screenshots for better explanation).
Steps to Reproduce -
- To reproduce this, you have to have two field behaviours in place similar to the screenshot I added below - I believe that any fields work for this except the summary.
- After creating the two behaviours, create one issue on the project your testing with. It doesn't matter what you put in this issue.
- After you've created this issue, click the create button while on that issue's view page so that a the create pop-up screen appears over the issue you made earlier.
- On this pop-up screen, add some text/content into the field that you made required with a behaviour earlier - in my screenshot I used the Description field.
- Press Create after doing this, make sure you don't add anything into the other field that you've added a behaviour on (FreeTextA in my screenshot) or the summary field.
- Create validation will fail, as expected. However, if you look at the field you have the read-only behaviour on (FreeTextA in my screenshot) the field will be read-only now even though you are still on the Create workflow action (see screenshot).