It's all about the answers!

Ask a question

Place restrictions so that only certain user roles may add work items to the backlog


Richard Tweed (811220) | asked Oct 01 '15, 3:28 a.m.

I need to be able to place restrictions, so that only certain user roles may add work items to a backlog.  Other user roles will need to be able to plan Sprints, so they will need permissions to change the 'Planned For'.

Is there a way that RTC can enforce this?

One answer



permanent link
Ralph Schoon (63.2k33646) | answered Oct 01 '15, 3:48 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please see the permissions in the project administration, where you can specify which role can and can not change specific attributes. For more information about Work Item customization see:






Comments
Richard Tweed commented Oct 01 '15, 5:28 a.m.

Thanks Ralph.  For this particular use case, we were looking at restricting the roles that could adjust the 'Planned For' attribute.  This works, as it prevents users from creating a work item and planning it for the backlog, however then prevents other roles from being able to move the work item from the backlog into a Sprint, and then create the Tasks that are Planned For that Sprint.

In short, what I'm looking to be able to do is;

1) Any user can create a work item, however may not set the Planned For value

2) The 'Product Manager/Owner' adds to the backlog does the ranking etc.

3) The 'Scrum Master' moves the item to a Sprint, creating the Tasks for that sprint etc...

Apologies if its contained within the link within the answer above, however I could not locate that.


Ralph Schoon commented Oct 01 '15, 5:37 a.m. | edited Oct 01 '15, 5:38 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You can only permit/limit setting an attribute for a role. You can't selectively select what values a role could set. In your case, allow the scrum master role and the product owner role to set the value for the iteration and prevent everyone else from doing it.

Personally I think an agile team should be able to handle this without such limitations. After all agile is all about trust, communication and coordination in the team. If the distrust in the team is so big that you have to limit roles doing this, the team is likely going to fail.

If you want an even more dynamic behavior e.g. limit roles to select iteration types, you would have to create a work item save advisor that checks this and prevents the save.
See https://rsjazz.wordpress.com/2015/09/30/learning-to-fly-getting-started-with-the-rtc-java-apis/ if you think this is necessary.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.