-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
By default, when a user is moving an issue to another project, the reporter of the issue must have a create issue permission
There are times when an issue is needed to be moved to another project, but the reporter should not have the create issue permission for that particular project. Therefore, I believe there should be a configuration whereby an issue can be moved regardless of the reporter's create issue permission. The move procedures can only be done by a JIRA administration.
As a scenario:
"I guess I think of it like this: Imagine if you guys created a project for "Issues raised by important customers" - and defined the permissions so that people like me couldn't create issues directly in this project, but a responsible atlassian administrator could move an issue that I raised into this project if I was discovered to be an important customer. Mr Atlassian Admin is carrying out his weekly review and moves 60 issues into this new project - and JIRA requests that he choose a new reporter for all 60 issues. Now you don't know who raised them!"
- is related to
-
JRASERVER-27198 Move Issue Configuration
- Closed
- relates to
-
JRACLOUD-15181 Make bulk move operation more user-friendly during field update stage
- Closed