Cloning JIRA issue gives the previous assignee mail that he/she has created an issue

[swati gupta]

Hi Team,

A user created issue-1 and B  user cloned issue-1 , but A user got e-mail stating that he has created an issue although he did not do that, but was instead cloned by B, but since earlier issue was cloned by B so she should get an e-mail not A.

This is a security compliance issue.

Kindly look onto this issue asap.

Thank You!!

[swati gupta]

@Sreenivasaraju P 

One more open question for me, 

Issues are moved from one Sprint to another even when the Sprint Is not completed (the issues not in Done status either move to Backlog or other chosen sprints when completing the sprint) and data is lost.

The problem could be that the Board used are Kanban boards which does not support the functionality.

The sprint ids also got lost in the project once the sprint is closed and says you do not have permissions to view the Sprint or it does not exists anymore.

Please be so kind to share your suggestions on the sprint/boards issue in JIRA and let us know if there are any changes made to the boards in new releases?

Please let me know if more inputs are required from my end in order to make the issue more clear?

Please help me, or let me know from where I can ask for help as the issue is very urgent for me

Thank You!!

[swati gupta]

@Sreenivasaraju P 

One more open question for me, 

Issues are moved from one Sprint to another even when the Sprint Is not completed (the issues not in Done status either move to Backlog or other chosen sprints when completing the sprint) and data is lost.

The problem could be that the Board used are Kanban boards which does not support the functionality.

The sprint ids also got lost in the project once the sprint is closed and says you do not have permissions to view the Sprint or it does not exists anymore.

Please be so kind to share your suggestions on the sprint/boards issue in JIRA and let us know if there are any changes made to the boards in new releases?

Please let me know if more inputs are required from my end in order to make the issue more clear?

Please help me, or let me know from where I can ask for help as the issue is very urgent for me

Thank You!!

[Sreenivasaraju P]

Hi @swati gupta ,

Please refer the document, It will help you to understand clone concept

• Reporter 
  (If you do not have the Modify Reporter permission, the clone issue will be created with you as the Reporter.)

https://confluence.atlassian.com/jira064/cloning-an-issue-720416353.html

Reporter is different from creator , in your case B name will come as creator and A name will come as Reporter.

[swati gupta]

Hi  @Sreenivasaraju P 

Thanks for answering this. I agree modify reporter gives the permission to change the reporter only after the clone issue is created.

But before that the person who was the reporter of the previous issue got an e-mail that he created the cloned issue, but cloned issue was created by someone else.

He treated it as a security compliance issue.

Can you please help me with this?

Thank You in advance for your support!!

[swati gupta]

@Sreenivasaraju P 

Hi,

Thanks for answering this. I agree modify reporter gives the permission to change the reporter only after the clone issue is created.

But before that the person who was the reporter of the previous issue got an e-mail that he created the cloned issue, but cloned issue was created by someone else.

He treated it as a security compliance issue.

Can you please help me with this?

Thank You in advance for your support!!

[Sreenivasaraju P]

Hi @swati gupta ,

While cloning the issue, jira will not give any option to choose the reporter. It will give the option to set summary only. 

As the person (who cloned the issue) has the permission to modify reporter. Jira automatically set the reporter of original issue as the reporter of cloned issue. You remove the modify reporter permission of the user. So the cloned request will not copy the reporter from original ticket.

One more point : If the user has the Modify Reporter permission , he/she can directly create jira ticket on behalf of any other user (Reporter as any other user). So in this case also creator will be different form Reporter.

[swati gupta]

@Sreenivasaraju P 

The person who has modify reporter permission in JIRA, cannot change the reporter of the cloned issue before cloning.

if a person does not have modify reporter person than also he cannot change the reporter of the cloned issue before and after cloning also.

So this does not solves our issue.

Was this helpful to understand my problem?

[Sreenivasaraju P]

Hi @swati gupta ,

Same thing i have mentioned in my earlier reply.

While cloning the issue, jira will not give any option to choose the reporter. It will give the option to set summary only. 

What i was trying to say go to your project permission schema and remove every one from the Modify Reporter permission. With this ,whenever any one try to clone any issue, he/she will become the reporter automatically. So you will not get any security compliance.

[swati gupta]

@Sreenivasaraju P

Thanks a lot for your reply, I understood it now.

One more open question for me, which has not been answered yet from May is:

Issues are moved from one Sprint to another even when the Sprint Is not completed (the issues not in Done status either move to Backlog or other chosen sprints when completing the sprint) and data is lost.

The problem could be that the Board used are Kanban boards which does not support the functionality.

The sprint ids also got lost in the project once the sprint is closed and says you do not have permissions to view the Sprint or it does not exists anymore.

Please be so kind to share your suggestions on the sprint/boards issue in JIRA and let us know if there are any changes made to the boards in new releases?

Please let me know if more inputs are required from my end in order to make the issue more clear?

Thank You!!

[swati gupta]

@Sreenivasaraju P 

One more open question for me, which has not been answered yet from May is:

Issues are moved from one Sprint to another even when the Sprint Is not completed (the issues not in Done status either move to Backlog or other chosen sprints when completing the sprint) and data is lost.

The problem could be that the Board used are Kanban boards which does not support the functionality.

The sprint ids also got lost in the project once the sprint is closed and says you do not have permissions to view the Sprint or it does not exists anymore.

Please be so kind to share your suggestions on the sprint/boards issue in JIRA and let us know if there are any changes made to the boards in new releases?

Please let me know if more inputs are required from my end in order to make the issue more clear?

Thank You!!

[swati gupta]

@Sreenivasaraju P 

One more open question for me, which has not been answered yet from May is:

Issues are moved from one Sprint to another even when the Sprint Is not completed (the issues not in Done status either move to Backlog or other chosen sprints when completing the sprint) and data is lost.

The problem could be that the Board used are Kanban boards which does not support the functionality.

The sprint ids also got lost in the project once the sprint is closed and says you do not have permissions to view the Sprint or it does not exists anymore.

Please be so kind to share your suggestions on the sprint/boards issue in JIRA and let us know if there are any changes made to the boards in new releases?

Please let me know if more inputs are required from my end in order to make the issue more clear?

Thank You!!