• Type: Bug
• Resolution: Fixed
• Priority: Medium (View bug fix roadmap)
• Fix Version/s: 6.0-OD-11/Beta1
• Affects Version/s: 4.4.1, 5.2.9, 6.0-OD-09
• Component/s: None
• Labels:

  • affects-cloud
  • affects-server
  • issuelinking
• Environment:

  PostgreSQL DB
  JIRA 4.4.1

1. 

   cantlink.png

   24 kB

   22/Sep/2011 6:45 AM

2. 

   permission-given.png

   11 kB

   22/Sep/2011 6:45 AM

[JRASERVER-25771] Single user with permission to Link Issues for a Project, is not allowed to Link Issues.

Collapse comment: Oswaldo Hernandez (Inactive) added a comment - 08/Apr/2013 3:51 AM, Edited by Oswaldo Hernandez - 08/Apr/2013 3:51 AM

Oswaldo Hernandez (Inactive) added a comment - 08/Apr/2013 3:51 AM - edited

Verified the fix on master.

The expected behaviour after the fix is as follows:

1. Given an issue, if the user has no edit permissions but does have link issue permissions, he should be able to add and remove issue links from the issue

2. Conversely, If a user has edit permission over an issue but no link issue permissions, he should not be able to add/remove links and the edit/create/transition screens should not display the issue linking system field

This was tested successfully against the UI and also using the resources in the JIRA REST API.

Expand comment: Oswaldo Hernandez (Inactive) added a comment - 08/Apr/2013 3:51 AM, Edited by Oswaldo Hernandez - 08/Apr/2013 3:51 AM

Oswaldo Hernandez (Inactive) added a comment - 08/Apr/2013 3:51 AM - edited Verified the fix on master. The expected behaviour after the fix is as follows: 1. Given an issue, if the user has no edit permissions but does have link issue permissions, he should be able to add and remove issue links from the issue 2. Conversely, If a user has edit permission over an issue but no link issue permissions, he should not be able to add/remove links and the edit/create/transition screens should not display the issue linking system field This was tested successfully against the UI and also using the resources in the JIRA REST API.

Collapse comment: Pawel Bugalski (Inactive) added a comment - 20/Mar/2013 1:45 PM

Pawel Bugalski (Inactive) added a comment - 20/Mar/2013 1:45 PM

This bug can also manifest itself the other way around:
1. Create user that can edit issues, but does not have permission to link issues
2. Observe as this user can link issues using the Linked Issues system field.

Expand comment: Pawel Bugalski (Inactive) added a comment - 20/Mar/2013 1:45 PM

Pawel Bugalski (Inactive) added a comment - 20/Mar/2013 1:45 PM This bug can also manifest itself the other way around: 1. Create user that can edit issues, but does not have permission to link issues 2. Observe as this user can link issues using the Linked Issues system field.

Collapse comment: David Fischer added a comment - 16/Dec/2011 5:13 PM

David Fischer added a comment - 16/Dec/2011 5:13 PM

I have the same problem. I have given Link Issue permission to the User role of my projects (basically, everyone). Users can therefore link issues to other issues using the "Link" action.
However, they cannot link issues during transitions (using the "Linked Issues" pseudo-field in the transition screen).
Of course, I have also removed the "Edit" permission from almost everybody - "Edit" is way too dangerous, I prefer to create a pseudo-transition that allows users to edit just the fields that are safe to edit.

This is the second time I run into a bug related to my users not having the "Edit" permission. The other bug is in GreenHopper, which doesn't allow users to "schedule" issues (i.e. drag&drop them onto versions in the planning board) when they don't have the Edit permission.
You should really test Jira in a configuration where not everyone has the Edit permission.

Expand comment: David Fischer added a comment - 16/Dec/2011 5:13 PM

David Fischer added a comment - 16/Dec/2011 5:13 PM I have the same problem. I have given Link Issue permission to the User role of my projects (basically, everyone). Users can therefore link issues to other issues using the "Link" action. However, they cannot link issues during transitions (using the "Linked Issues" pseudo-field in the transition screen). Of course, I have also removed the "Edit" permission from almost everybody - "Edit" is way too dangerous, I prefer to create a pseudo-transition that allows users to edit just the fields that are safe to edit. This is the second time I run into a bug related to my users not having the "Edit" permission. The other bug is in GreenHopper, which doesn't allow users to "schedule" issues (i.e. drag&drop them onto versions in the planning board) when they don't have the Edit permission. You should really test Jira in a configuration where not everyone has the Edit permission.