New 3.0.1 'Delete Work Item' requires JazzAdmin rights?
Which is required to see the new "Delete Work Item" menu option in RTC 3.0.1?
(1) Administrator of the project area -or- (2) JazzAdmins? The reason we ask is ... the "Deleting Work Items" section in RTC 3.0 Information Guide (http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=/com.ibm.team.workitem.doc/topics/t_deleting_work_items.html) states ... "You must be an administrator of the project area in which you are attempting to delete work items, and you must have team area permissions to delete work items assigned to that team area". But then it goes on to say ... "If you do not have these permissions, the Delete buttons do not appear as indicated in the steps below. Add the JazzAdmin role to your user id and set the delete permissions in the Team Area specification editor." So which is it? Administrator of project area -or- JazzAdmin? The two are drastically different. We don't give away JazzAdmin rights to our end-users as this will provide much more than Delete Work Item, for example, access to the CCM & JTS ADMIN UI (Advanced Properties - yikes). Thanks, Tim |
8 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 25 '11, 3:04 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
It is my understanding that the latter is correct, i.e. that you need to
both: - belong to the JazzAdmin repository group - have a role in the project that has permission to perform the "delete work item" operation. So in particular, I believe that statement that you need to be "an administrator of the project area in which you are attempting to delete work items" is incorrect. I've submitted work item 172307 to get the documentation fixed. Cheers, Geoff On 7/25/2011 12:23 PM, timothy.mulligan wrote: Which is required to see the new "Delete Work Item" menu |
Hi Geoff,
Thank you for clarifying. I agree the 3.0 Information Center documentation needs to be fixed. I am disappointed that this new feature is only available to the JazzAdmin role because in an enterprise implementation of RTC such as ours, that essentially makes this new feature unavailable (useless) to normal end-users. -Tim It is my understanding that the latter is correct, i.e. that you need to Which is required to see the new "Delete Work Item" menu |
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 25 '11, 9:34 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd suggest the following:
Create a "RecycleBin" project area, and have normal users just move their junk work items to the RecycleBin project area. Then you can have an Admin run a script every so often to purge old work items that are still in the RecycleBin project area. This provides a first-level safety net for project area administrators that want to "undo" a work item deletion. If this doesn't work out in practice, you can also submit an enhancement request to get this functionality changed. Cheers, Geoff On 7/25/2011 3:53 PM, timothy.mulligan wrote: Hi Geoff, |
The "Results" and "What to do Do Next " sections in https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.team.workitem.doc%2Ftopics%2Ft_deleting_work_items_web.html seem conflicting to me, too.
I'd suggest the following: Hi Geoff, |
I'd suggest the following: Hi Geoff, Hi Geoff: I agree with your approach and it's much safer. The artifact could be linked to code or other work items and you want to really be careful about what gets deleted. In regards to your solution, do you mean Project Area or an Iteration? I usually create an Iteration called "Recycle Bin" and then just change the "Planned for" to "Recycle Bin" to make the item disappear from a plan. It's a little simpler and it's easier to find and restore the work item since it in the same project area. It also prevents possible incompatibles between work items in different project areas. And as you mention above, periodically the admin will delete work items in the Recycle Bin. |
Geoffrey Clemm (30.1k●3●30●35)
| answered Aug 12 '11, 11:25 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Either a Recycle Bin Project Area or Recycle Bin Iterations are fine
with me, but some reasons I prefer a single Recycle Bin Project Area: - I don't want these items to be found when I run a query (and don't want to add a special term to all my queries to ignore items in a Recycle Bin iteration) - I don't want to create a Recycle Bin Iteration in every project area I work in. - For the periodic purging, I don't want to have to separately query each project area for work items to purge. I agree that moving to another project area can mutate some of the fields, but they're available in history if I have to restore them (normally, I don't restore work items from the recycle bin ... I delete them). But either way is OK with me. Cheers, Geoff On 8/12/2011 4:23 AM, rknaste wrote: gmclemmwrote: Hi Geoff: I agree with your approach and it's much safer. The artifact could be linked to code or other work items and you want to really be careful about what gets deleted. In regards to your solution, do you mean Project Area or an Iteration? I usually create an Iteration called "Recycle Bin" and then just change the "Planned for" to "Recycle Bin" to make the item disappear from a plan. It's a little simpler and it's easier to find and restore the work item since it in the same project area. It also prevents possible incompatibles between work items in different project areas. And as you mention above, periodically the admin will delete work items in the Recycle Bin. |
The doc on deleting work items is unclear as to which permissions are required. Turn out you need to be in either the JazzAdmins or JazzProjectAdmins repository group for the 'Delete Work Item' item to appear in the work item editor's title menu. I've filed 177778: Clarify documentation for deleting work items: which permissions are required?.
|
I see one limitation on the Recycle Bin solution... need to double check if I am correct.
Using the web client you can "Move or copy this WI to another PA" only 1 work item at a time, but you don't have ways to do that by selecting multiple work items at once. Is this correct? Scenario: if someone created work items using a WI template that was not the one s/he wanted to use (e.g. selection error), it will create a bunch of work items at once. But then, you have to go 1 by 1 to move it to another PA. * How could you manage this scenario with the web client? (I don't want to give my end-users the JazzAdmin permission, but they need to get rid off those WIs in some way). Is there any way to move several WIs at once, and I did not find how to do that? * If moving multiple WIs at once is a tool limitation, is anybody aware of an existing enhancement to have this? I feel it could be really useful... Thanks, --Claudia |
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.