It's all about the answers!

Ask a question

Component/stream ownership and Save Work Item preconditions


Mark Castro (741219) | asked Oct 10 '14, 2:46 p.m.
Hi all

Basically we have teams within project areas that would like to configure separate Save Work Item Preconditions for their streams.
The components in some of the streams are owned by other teams, however.

If we make the Team with the customized preconditions the owner of the stream, would these preconditions cascade down to all of the components in the stream?
Or would we have to make the Team in question the owner of the components as well?

I did some testing and it appears that the Component owner's preconditions overrule the stream owner's, but would like to confirm & also see any potential documentation that exists on this.

Hope this makes sense. Thanks for any help!

Accepted answer


permanent link
Geoffrey Clemm (30.1k33035) | answered Oct 11 '14, 11:48 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The "Save Work Item" process that applies to a work item is determined from the Team Area of that work item (not the owner of some stream).   On the other hand, the "Deliver" process that applies to a stream is determined from the team area that owns that stream.    The owner of a component determines the process for the "save component" operation (but there aren't many things you can do with a "save component" operation, beyond renaming and changing the ownership of a component).

So when you say "the Component owner's preconditions overrule the stream owners", that doesn't really make sense.  In particular, if it is a "Save Work Item" precondition you are interested in, that isn't affected by either a Component owner or a Stream owner ... it is affected by the Team Area of the work item.

Mark Castro selected this answer as the correct answer

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.