-
Suggestion
-
Resolution: Unresolved
-
9
-
20
-
Currently, only user with Edit Permission in the projects able to add issues to sprint.
However, there are some use case where by projects are interrelated and the other project dependent on other project's issues to be resolved. So, having the ability to nominate an issue to be fix in the next sprint in another project is important in this scenario.
- incorporates
-
JSWCLOUD-13025 Having a separate permission for Active sprint and Planned sprint
- Closed
- is duplicated by
-
JSWCLOUD-6388 Restrict 'Remove Issue from Sprint' operation to users with Schedule permission / Administer Projects permission
- Closed
-
JSWCLOUD-10747 As a scrum master, I would like to restrict permissions on adding tasks to Active Sprints
- Closed
-
JSWCLOUD-15093 Only some users should be allowed to add issues to Active Sprints (Scope Change)
- Closed
- is incorporated by
-
JRACLOUD-69298 Allow fields to be hidden/edited when certain group or users views a ticket i.e field-level security
- Gathering Interest
- relates to
-
JSWCLOUD-5035 As a JIRA/GH administrator, I would like to be able to specify who is allowed to create and start a sprint independently from the "Administer Projects" JIRA permission
- Closed