It's all about the answers!

Ask a question

No UI for configuring preconditions/followup of

Gabriel Lopez de Armas (10189) | asked Dec 17 '13, 6:45 a.m.
We are in a situation where we want to implement a precondition when saving "save project area". 
We sadly discovered that "saveTeamArea" operation doesn't apply when saving the project area itself, and there wasn't any other operation that seems to suit in the "Operation behavior" configuration inside the "Process configuration" tab of a project area.

But by doing some searching*, we found out that there is operation, but it doesn't have a way to be configured through the UI. We tested it and it works. 

Our use case is to disallow the use of certain roles. There are certain roles that we prefer normal users doesn't have (just certain devops), but we still want Area administrators to manage users by themselves (only disallowing assigning those concrete roles).

Is there a reason it is not present in the UI? Can it be added to it in the future?

Jim Ruehlin commented Dec 17 '13, 9:04 p.m.

Can you clarify what your use case is here? Are you trying to prevent a certain role from saving the project? Or are you trying to stop the project from being saved if it includes some type of role?

Gabriel Lopez de Armas commented Dec 18 '13, 4:49 a.m.

The second. 

We want only JazzAdmins to be able to assign a certain role, while still allowing team leaders/project managers to modify the members of a project (and assign any roles except that one)

4 answers

permanent link
Ralph Schoon (63.3k33646) | answered Dec 17 '13, 6:49 a.m.
I would assume that it is internal and always configured. 
See for how to extend RTC and follow the link "Find Extensions Points and operation ID’s; see this Wiki Entry for extension points and operation ID’s; look into the Interesting Links page for more hints" to have a look which operations you can hook up to.

Gabriel Lopez de Armas commented Dec 17 '13, 8:58 a.m.

Thanks for the reply. 

My concern is not how to implement it, but more on why it is hidden. Essentially, because it is harder to maintain the configuration. For knowing if the project is configured with our precondition we would need to check the XML configuration.

Ralph Schoon commented Dec 17 '13, 9:11 a.m.

I would assume because all non hidden stuff needs to be documented etc. People would ask for more UI options and the like. At some point that s impossible to maintain. You can decide to create an enhancement request for your use case.

permanent link
Qiong Feng Huang (76911610) | answered Dec 25 '13, 11:27 p.m.
 There is no way to configure pre-condition or follow-up action for saveProject operation right now. This is the expected behavior. We don't support it because we have no need for a pre-condition for it.

Martin Wassermann commented Jun 16 '14, 9:00 a.m.

There are other actions in the UI that have no pre-conditions or follow-up actions (e.g. Display Report (server)). So I did not really see the difference.

permanent link
SEC Servizi (97123860) | answered Dec 27 '13, 3:49 a.m.
We don't support it because we have no need for a pre-condition for it.
We have need of follow-up action to be able to run our own customization in project areas. ;)
We use it with success, even we notice a strange behavior: if the current user is not a member of the project area, but he belongs to JazzAdmin, he can save the project area (got ovverride permission message) but the follow-up action then is not run.

permanent link
Martin Wassermann (13864144) | answered Jun 16 '14, 8:54 a.m.

We have a need of this extension point too, because "saveTeamArea" is not called when you e.g. add a user in the project area itself. 

We have the same use case like the thread creator. And therefore we have to use the precondition with "saveTeamArea" and "saveProjectArea".

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.