Before today, this user was able to see all the fields on an edit. Today when he edits, he can comment or change the assignee.
Other users (admin or not) can edit the issue and see all the fields. The configure fields button (for whatever reason) is not on the screen.
What could the issue be for just this user? I even made him an ADMIN to test and he was still limited to the above two fields.
Ok, that proves it's his account, and nothing structural.
Could you use the developer console in a browser to work out where the "hidden" tag is coming from? Or even if the fields are there in the html at all?
Ok, that's handy, but those fields are the ones in the "configure fields" drop-down box, so I'd expect them to be hidden if the button is missing.
This is all pointing to something broken behind the show/hide options in the "configure fields" - is this consistently not appearing for all issues for this user?
Still not making headway (luckily we have a work around).
I decided to query the database table (customfield) looking for any description with this user or the word user or group in it and there are none.
Anything I could try to find from the backend?
This may come with me to the Summit!
That's a good call on the custom field, there might have been a clue in a user-picker.
I'm thinking it's more likely to be something in the data that is stored for them that relates to the "configure fields" option. I think that might be in one of the "property" tables, and linked to his id.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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