So I am sure this is a simple permissions thing but I can't for the life of me work out. And it's also not me that's having the problem, it's one of the guys on my scrum team.
I'm the admin that should be able to work it out... but just can't.
So he clicks into the description field on an existing issue and edits the content - all good so far. He then hits 'save' - no error, appears to accept change although when the field reloads, the changes are not there.
He has the same permissions as the rest of the team and he is the only person with this issue so maybe I'm not missing something obvious but has anyone else seen this?
Hello,
There is no permission like this. Maybe you have custom listeners in your Jira, which rollback changes.
OK, thanks so much for taking a look Alexey - I’ll see what I can find but good to know it isn’t a permissions issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This same thing is happening to us, but only for some projects, even though they share the same issue types, screens, schemas, and configurations. There is some really serious bugginess in the description field in our JIRA cloud. JIRA seems to be clueless about it even though people are mentioning issues. The problem is it isn't reproducible easily as I mentioned you can have a complete clone of one Project where it isn't happening.
Enter text.
Click Save
Still says unsaved changes
Refresh page or change status and content disappears.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.