-
Suggestion
-
Resolution: Duplicate
-
None
As mentioned in the docs, Project Administrator permission is required. This is not great from a security perspective as anyone that can release could mess up (unintentionally) all the project config.
| You will need to have the JIRA 'Project Administrator' |
We should be able to use the Permission Schemes to assign specific groups the role to create release versions and release via Rapid Board.
- duplicates
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Closed
[JSWSERVER-4701] Allow non project admin users to release from Rapid Board
Viðar Svansson [Tempo]
added a comment - A simple solution that would be similar to what we do in Tempo is to have a global configuration for which users can be board admins. This would default to "project admin" like now but would allow you to select different role. The user would then need this role in all the board's project just like he needs to be project admin in all the projects.
Viðar Svansson [Tempo]
added a comment - A simple solution that would be similar to what we do in Tempo is to have a global configuration for which users can be board admins. This would default to "project admin" like now but would allow you to select different role. The user would then need this role in all the board's project just like he needs to be project admin in all the projects. Viðar Svansson [Tempo]
added a comment - Please consider to update the priority of this story. It makes it impossible to do agile and time tracking in certain countries. So companies need to decide if they want to use GreenHopper or a time tracking solution like Tempo.
Viðar Svansson [Tempo]
added a comment - Please consider to update the priority of this story. It makes it impossible to do agile and time tracking in certain countries. So companies need to decide if they want to use GreenHopper or a time tracking solution like Tempo. Viðar Svansson [Tempo]
added a comment - Like described here, this makes it impossible to enforce certain privacy settings. For example, Scrum Masters are not allowed to view worklogs of other team members. If the worklogs are restricted to a project role, then the Scrum Master is able to assign himself to the role required to view the worklogs. This is a major problem in countries where law dictates that employees are not allowed to see other people worklogs (i.e., in Germany).
Viðar Svansson [Tempo]
added a comment - Like described here , this makes it impossible to enforce certain privacy settings. For example, Scrum Masters are not allowed to view worklogs of other team members. If the worklogs are restricted to a project role, then the Scrum Master is able to assign himself to the role required to view the worklogs. This is a major problem in countries where law dictates that employees are not allowed to see other people worklogs (i.e., in Germany). 
Can you guys please implement a proper permission setup so other plugins don't break?
We have problems doing agile, because we also need Tempo installed and apparently we cannot obey the law in Germany because of... GREENHOPPER!
https://answers.atlassian.com/questions/160757/can-i-restrict-access-to-the-project-report
Copying sclowes who is usually quite responsive.