I am having issue committing issues within Jira plans (portfolio?). This hasn't always been the case, and no changes have been made to the workflow or field screens that I am aware of that could be potential blockers. When I try to review changes within the plan, and commit them changes I am hit with the following error message,
"Could not be committed for unknown reasons"
Has anyone else had this issue occur and know of the fix? I have scanned across a few community questions but haven't come across anything that has resolved the issue.
Even i notice the same issues.. after i have upgraded to new portfolio plugin 3.29.1, all the users are complaining that it was working earlier and now it is throwing error for the same creating new issues or updating the issues.. it throws the same error "Could not be committed for unknown reasons
Hi Shylaja,
I believe I have a resolution to this. I don't know if this had come as part of the upgrade, as previously I had no issues committing the changes.
However, within the permission scheme of the project which the plan related too, the permission for "Schedule Issues" contained a group that I was not part of, even though down as an Admin. I added myself to the group and was able to commit the change. I am not sure if this was something that had been amended internally, as previously I had no issues committing or is relation to the update, but it may be worth trying, to either add a new group to the Schedule Issue permission, or adding yourself to the group that is currently in there.
Cheers
Steven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks this method worked for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.