Details
-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Description
Summary
In JSW projects, adding the jira.permission.edit.denied or the jira.permission.edit.user=<user> property to a step in the workflow disallows you from editing that issue but does not stop your from modifying issues associated with it. For example, an Epic issue that has a workflow that blocks editing for other users does not stop them from moving stories out of the Epic.
Environment
- JIRA v1000.383.3
Steps to Reproduce
- Create a Project (Project1)
- Create an Epic in the Project (Epic 1)
- Create an issue (Story1)
- Assign Story1 to Epic1
- Go to Workflow administration: https://<instance>/secure/admin/workflows/ListWorkflows.jspa
- Click add workflow (Epic workflow)
- Add status 'In Progress' and make sure we can get to this Status by setting all status' are able to transition into this
- Click In progress
- Click Properties
- Add property: key: jira.permission.edit.user value: <username>, e.g. jashmore
- Go to Project1 - Project Settings - Workflows
- Add workflow (Epic workflow)
- Assign this workflow to the Epic Issue type
- Go back to the backlog
- Transition Epic1 to In Progress
- See that we cannot not add issues to Epic1.
- Try to move issues out of the Epic, which is allowed
Expected Behavior
The story should not be able to be removed from the Epic
Actual Behavior
JIRA allows the issue to be removed from the Epic.
Workaround
None so far
Attachments
Issue Links
- relates to
-
JRASERVER-45973 'jira.issue.editable=false' property does not impede editing of issues
- Closed
- is duplicated by
-
HELIX-516 Loading...