It's all about the answers!

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

×42,884
×6,115

question asked: Feb 03 '13, 10:33 a.m.
question was seen: 4,734 times
last updated: Jan 17 '17, 8:30 p.m.

Related questions

Error: " Cannot save the work item template on the server." when trying to create WI template

0
Yvo Van Wezemael (9●10●12) | asked Feb 03 '13, 10:33 a.m.
JAZZ DEVELOPER
When trying to create a WI template we get the error mentioned above. Permissions are OK (i.e. the user has "Modify a Project Area" rights.

Note that the project area re-uses the process of another project area, nothing is overwritten. I tried to create a WI template in the supplier of the process (wit h a user having the same role there) and it worked:

Any idea?
Comments
Michael Reed commented Jan 17 '17, 8:28 p.m. | edited Jan 17 '17, 8:30 p.m.

 Hi Yvo and Eric,


I'm curious if you know the extent of the issues that might arise if you forget to keep <project-configuration> </project-configuration> in the process template when sharing from a master.

Please keep in mind that I found this forum topic because I did just this and now I'm curious to better understand what other unintended issues may have come into play if I hadn't found this.

Thanks!

-michael

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Eric Jodet (6.3k●5●111●120) | answered Feb 04 '13, 1:19 a.m.
JAZZ DEVELOPER
Hello Yvo,
not easy to tell you what could be wrong here.
I would need to check on various settings like:
- Project Areas inheritance
- user / role permissions in both PAs
- check if Work Item Template is "finalized" in the shared PA

Thanks.
Eric.

Comments
Eric Jodet commented Feb 07 '13, 3:43 a.m.
JAZZ DEVELOPER

Hello Yvo,
glad you fixed your issue.

Thanks.
Eric.

0
permanent link
Yvo Van Wezemael (9●10●12) | answered Feb 07 '13, 3:37 a.m.
JAZZ DEVELOPER
Hello Eric,

thanks for your answer. We found the reason in the meantime:

The project area consuming the other process had the following configuration source:

...
<process-specification xmlns="http://com.ibm.team.process">
</process-specification>

where it should have been

...
<process-specification xmlns="http://com.ibm.team.process">
    <project-configuration>
    </project-configuration>
</process-specification>

If I remember correctly, we removed an overwrite of the process once and obviously deleted a little to much.

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.