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
Josh Devenny and Roy Krishna
JIRA Product Management

Anton,

I realize that you have lots to do (I also voted for some of those popular issues) and thank you for taking this improvement into consideration.

Cheers,
Aleksey

Aleksey,

Thank you for your input, and please accept my apologies for the delay in replying. Things have been very busy here.

I can see your point and I think I agree. I must admit that in the past I have been very sceptical of generating 2 events for one action. That is, generating a MOVE event followed by a CREATE event when an issue is moved. The reason for this, is that it makes writing custom Issue Listeners a little harder and more confusing.

In this case, however, I do not really see any other good way of letting users of the source project know that an issue has been moved. If we do implement this feature, I guess authors of Issue Listeners will have to take into account that a MOVE event is followed by a CREATE event.

The other side affect of generating 2 events, is that some users might receive 2 e-mails, one for MOVE event and another for CREATE event.

Aleksey, I must admit that we have a lot of feature requests. For popular issues please see:
http://jira.atlassian.com/browse/JRA?report=com.atlassian.jira.plugin.system.project:popularissues-panel
and therefore it will be a while until we will be able to get this done.

I would like to extend a personal thanks to you for your feedback and your time. It will definitely help us.

Cheers,
Anton

Anton,

Thank you for your quick response.

When an issue is moved to another project, to me it seems like it should be two events - a MOVE event on the previous project and a CREATE event on the destination project.
I believe that these two events should be treated separately as far as notifications are concerned: the previous project's notification scheme for the MOVE event and the destination project's notification scheme for the CREATE event.

The notification sent out on the MOVE could contain the information from the previous project with updated values only for the destination project's name and the destination issue key.
If this is still too much information and poses a security problem, the notification could just inform that there has been a move with no information on the destination project. The reporter or watchers of the previous project receiving the notification will follow the previous issue's link in the e-mail. After that, everything would happen as it does now when you try to access a destination issue with the previous issue's key: the user is redirected to the destination issue and receives an error message at which point they will contact the administrator. The important thing is that they know something happened on their issue.

The CREATE event notification on the destination project could be left as is since there's no problem on that end.

Cheers,
Aleksey

Aleksey,

You are right. At the moment we do not send notifications to users who cannot see the issue.

What do you think is the best way to solve this? After the issue is moved into a new project the notification scheme of the destination project is used to work out who should be notified. Should we use the notification scheme from the previous project to work out who to notify? What information should be sent to the users who no longer have permissions to see the issue? For example, do we send all the issue field information or only let them know that the issue is moved? I am a bit concerned if we send information about the issue to users that should not be able to see the issue.

Cheers,
Anton