We had created specific field configurations for individual issue types, with the intent of making sure only the appropriate fields for each type were displayed when creating tickets.
Recently, it has come to light that we are getting different user experiences within our Jira instance, where some fields have suddenly vanished for users without warning. There does not seem to be a pattern to it, and it results in the affected users needing to switch off the "User request type fields" option, go to "Show fields" and re-add everything they need by using the checkboxes there to show fields that were never previously hidden.
This has only started happening in the past week or so, and it is not affecting all users at the same time.
We first noticed there was something unusual happening when trying to add a new custom field to a specific issue type screen, While the "Find my field" showed that everything had been created correctly and was in the right place, two people were able to see it as intended, and two others had to physically add the field by going to the "Show field" option. While I can sort of understand needing to add that new field via the Show fields option, it does not explain why fields that were always shown previously are now having to be manually added by multiple (but not all) users.
EDIT TO ADD:
Where the Use Request Type fields option is set, then it is not possible to set personal customisation of fields. It's meant to show all the fields, in the order set, for that request type.
If I try and find the field in question, Jira suggests that everyone is as it should be, and the field should be there, and while it is for some, it's not for others - and those for whom it DID show were reporting the next day that it was not. The only way to workaround this issue at the moment is to switch off the use request type fields option and then set field preferences manually.
Hi @kay bickell
It sounds like some users have customised their screen to not show all fields - customisation which is per-user, rather than site-wide.
Are the 2 users who see the new field as intended using a custom list of fields? Or are they just viewing all fields?
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ah, I see what you mean - sorry I wasn't clear.
We first noticed it when out of the four of us, two saw one thing, and two saw something else. One of those who didn't have missing fields (sorry for the double negative there) ended up with fields missing the following day, without having made any changes to customisation.
The issue has proven to be wider spread than just two users now, but is still not the same behaviour seen by ever user - and most of them would not know how to customise their screens anyway - they rely on us having created screens that have all the fields they need.
It started around the same time as a notification about some "Create issue" experience update being rolled out by Atlassian (notification seen on 13th November), but whatever this update was didn't have any further explanation of what it meant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @kay bickell
As it's intermittent, it might be difficult to replicate this.
I'd suggest contacting Atlassian Support in this instance, and seeking their help to resolve this!
Let us know what the outcome is :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rightio - don't suppose you have any idea what this "Create issue experience update" they mentioned on 13th actually entailed? I haven't found anything yet, although I could just be looking in the wrong places
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @kay bickell
I think it's part of a long-term roll-out - if you check this release blog from July, it's also mentioned on there.
Ste
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.