Changing issue rank in Advanced Roadmaps not working for some issues

[Kathy Hart]

I'm changing rank on issues in a Plan using Advanced Roadmaps. 

The issues come from several different projects, but all the projects are company-managed software projects. 

When I committed the changes, all the issues were updated except 3. I get this message on the final 3. 

Contacting my administrator doesn't help, because I AM the administrator. LOL

I'm trying to decide what the "unknown reason" could be. The only thing I can think of is that the issues have Security applied so that only the Assignee and Reporter can see them.

Would this affect Advanced Roadmaps ability to alter the Rank?

Thoughts?

Other reasons that might cause an issue with ranking?  

[Nic Brough -Adaptavist- · Accepted solution]

If you change the reporter from "current person" when creating an issue, you will find they are, well, the reporter.  So they get notified as though they had raised it themselves.

[Clemens Kleibusch]

Thanks Nic, I figured out that not the notification is the problem: the reporter when creating an issue can be any user independent of permissions. This is a bug for sure. If the reporter has permissions on the project he will be notified.

By the way, where can I report my first bug?

Thanks again, Clemens

[Nic Brough -Adaptavist-]

I don't think it's a bug - if you have people who can "set the reporter", they're doing it for a reason, probably along the lines of a helpdesk call (someone calls in, the agent raises an issue for them).

With the advent of Service Desk though, I don't see a lot of point in allowing the ability to set any reporter, I'd limit it to "people with create issue permission in the project", to bring it in line with the rest of the permissions.

To raise it though, visit https://jira.atlassian.com

[Clemens Kleibusch]

We don't have a real problem with that. So I decided not to raise it.