It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,882
×7,478
×6,113
×382

question asked: Mar 16 '17, 1:44 a.m.
question was seen: 2,592 times
last updated: Mar 16 '17, 3:33 a.m.

Related questions

Hi can we avoid the creation of new WI's related to changes set when we add new code on the window is this feasible?

0
rashmi k (13●3●18) | asked Mar 16 '17, 1:44 a.m.

 Hello,
using source code functionality, we have to use a changeset and a WI when we add new code to the repository.
About WI, by default we can use an existing WI or we can create a new one.
For one Project, we would like to avoid the creation of new WIs on that window.
is this feasible? if yes, how?
Thanks in advance

Please guide us related to above?

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Mar 16 '17, 3:33 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 It is basically your choice if you use a new or an existing work item - the dialog does not decide the user does. The only limitations that can be set up by the process owner is with the built in operation behavior advisors

  • Prevent Linking to Approved Work Items
  • Prevent Links by Approvers
  • Restrict Associating to Active Change Sets
  • Restrict Associating to Closed Work Items

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.