Though admin rights have been granted to the respective projects, commits made in JIRA Portfolio vanish directly after the commit has been made for certain projects.
For example, if we assign a theme to an issue and commit this change, the change is reverted on the Portfolio plan.
What causes this problem and how can we fix it?
Could you help us understand a bit more about the situation.
In your themes example, lets say you set the issue from theme A to theme B, then commit. Is it going back to theme A? Or is something else happening?
Does the change show in the commit dialog? After clicking 'commit' what happens?
It has been quite a while and the error has not happened again. It would be quite complicated to reproduce as I cannot remember neither Portfolio version nor the Jira projects affected at that time. The issue can be looked as resolved from our side.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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