When I/we clone a request, the reporter field is not updated with a "new" reporter - the person who is cloning the request should become the reporter.
I have looked through everything I can possibly find on this issue and all the answers I find say that if a user DOES NOT have modify reporter permission, then the reporter on the cloned request should become that user/current user.
This does not work. And I don't think that it has ever worked (at least not for us). I have modify reporter permission. When I clone a request, the reporter is still the same one as on the previous request, but I can change that after the clone request has been created.
When another user, that does not have modify reporter permission, clones a request the reporter is not changed to current user on the cloned request (new request.
Are we doing something wrong?
Found this on this site but I don't feel it answers the question.
I just tested this and if I clone an issue with a user that has Modify Reporter permissions the reporter stays as the original reporter. If I clone an issue as a user that does not have the Modify Reporter permissions I do get a warning stating the user will be the reporter and it creates the ticket with that person as the new reporter:
Thank you for your response.
Ok, looked into users and roles and permissions for a certain project. And then the groups the specific user is a part of.
When I look at Users and roles and look at the groups that are under "Modify reporter", the specific user is in neither one of those groups. However, if I go to permissions, I see that the project role for modify reporter in Permissions is both Administrator and modify reporter roles. And the specific user is in a group that is under the Administrator role in Users and roles (that group is not under the role modify reporter in Users and roles).
Could this be the problem? The user does not get any notification that she does not have "Modify reporter" permission and the reporter is cloned as well.
I tried this myself, and as you said, as soon as I took away my permission to modify reporter, I got the notification and became the reporter.
Really hope you understand what I am trying to say.. If not, please let me know.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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