It's all about the answers!

Ask a question

Follow-up Actions


Marco Bormann (16111910) | asked Jun 01 '10, 9:02 a.m.
I would like to define the following follow-up action: for each work item being saved it should be copied to another project (which will in each case be the same). Unfortunately the options in the different Operation Behaviour menus seem to be quite limited. Is there any way to get such a function?

Thanks,
Marco

3 answers



permanent link
Qiong Feng Huang (76911610) | answered Jun 01 '10, 9:02 a.m.
JAZZ DEVELOPER
I think you could contribute a new follow up action for the save workitem
operation. For detailed description on how to contribute a new follow-up
action, please refer to:
https://jazz.net/wiki/bin/view/Main/PreconditionFollowupCreation#Follow_up_Actions
and
https://jazz.net/wiki/bin/view/Main/TeamProcessDeveloperGuide#Adding_New_Operation_Participant.

Hope this can help you.

permanent link
Geoffrey Clemm (30.1k33035) | answered Jun 01 '10, 10:02 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'll defer to the work item customization experts on an answer to your
question, but a couple of questions to understand your use case better:

Do you really want a new copy of the work item created in another
project area every time you save a work item, or only every time you
create a new work item?

Once you have the copies created, should they have any relationship to
the originals, or are they now completely independent?

Cheers,
Geoff


On 6/1/2010 9:08 AM, MarcoB wrote:
I would like to define the following follow-up action: for each work
item being saved it should be copied to another project (which will
in each case be the same). Unfortunately the options in the different
Operation Behaviour menus seem to be quite limited. Is there any way
to get such a function?

Thanks,
Marco

permanent link
Marco Bormann (16111910) | answered Jun 01 '10, 10:41 a.m.
Thanks for your replies.

You are right Geoff, I only want the copy when a new work item is created and a link between them, but an update of the clone on a save would also come in handy.

This sounds pretty demanding but it actually should only replace the absent option of declaring attributes private and unreadable for some users who would only get access to the clones in a different project.

Marco

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.