-
Suggestion
-
Resolution: Won't Fix
-
QA Bamboo build 490
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Steps:
1. Login to JIRA and create a permission scheme.
2. Set browse project permission as "Current Assignee"
3. Please refer to permission screenshot for other permissions.
4. Associate the permission scheme to a issue and create a issue and sub task.
5. Login user can assign issues.
6. Assign the sub task to some other user.
Result:
1. User gets a big error message "It seems that you have tried to perform an operation which you are not permitted to perform." though the issue is currently assigned to the other user.
2. It seems that after assigning the user when JIRA try to show the issue, its unable to do due to permission and give this error message which is misleading.
3. Giving browse permission to all users solve the issue but its important as "Current Assignee" is an option in permission list.
Expected:
1. No error message and scenario should be handled gracefully.
- is related to
-
- Closed
-
- Closed
[JRACLOUD-20092] JIRA gives a permission error while assigning issues if browse permission is set only to "Current Assignable"
I'm not sure this is actually a bug. Are you saying the error message should be better worded?
I understand it's a little awkward, however viewing an issue is not permitted by the permission scheme, agreed?
There is currently no way to see that an operation has done anything except to return to a screen which always requires the browse permission. When you return to a screen you see the current state of the issue and therefore see that your operation has completed.
The error message does not distinguish between a workflow transition and a "view issue" "operation". So it is the latter that it is referring to. The message is the same regardless of what the user is attempting to do or why the permission is not granted. It doesn't detect that the permission has suddenly disappeared as a result of an operation that the user did.
I think this is an improvement request.
Hi,
This is a bulk update to specific issues in the JIRA (JRA) project
As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.
Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com
If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.
Best regards
Roy Krishna and Josh Devenny
JIRA Product Management