It's all about the answers!

Ask a question

Approvals tab - One rejection all rejected


Nigel Hopper (1032625) | asked Dec 23 '09, 12:35 p.m.
Hi

We are looking for a way to configure the approvals in work items. We are using this tab for approvals and reviews as designed, but find that when one person in a list of approvers rejects it, then an e-mail is sent to everyone saying that the whole thing has been rejected.

I guess there are two parts to this. The way we are using this is to advised people to reject something until it has been updated to reflect any changes that they are looking for. When that has been done they can then change it to approved. Trouble is people are getting the e-mail and thinking the whole thing is rejected (because only one person has rejected it) and so are not even looking at it. If they just made comments to get it updated, you have to check all the comments to see if they have reviewed it, when looking at the list it is much easier to see if they checked it.

What we are looking for is a way to configure the overall approval. For example, the overall approval/rejection does not change based on any of the related approvals / rejections, but is set by the owner of the work item.

An alternative would be to add a fourth alternative to the list of Pending, Rejected, Approved such as Reviewed which only means you have checked it and perhaps are waiting changes as described. Can this be done?

Cannot see how to do either, but it would make our lives a whole lot easier. Otherwise you are effectively controlled by one person who might enjoy rejecting things! (OK poor joke, but happens!!).

Thanks, Nigel.

3 answers



permanent link
David Olsen (5237) | answered Dec 24 '09, 1:23 a.m.
JAZZ DEVELOPER
NigelLH wrote:
We are looking for a way to configure the approvals in work items. We
are using this tab for approvals and reviews as designed, but find
that when one person in a list of approvers rejects it, then an
e-mail is sent to everyone saying that the whole thing has been
rejected.

I guess there are two parts to this. The way we are using this is to
advised people to reject something until it has been updated to
reflect any changes that they are looking for. When that has been
done they can then change it to approved. Trouble is people are
getting the e-mail and thinking the whole thing is rejected (because
only one person has rejected it) and so are not even looking at it.
If they just made comments to get it updated, you have to check all
the comments to see if they have reviewed it, when looking at the
list it is much easier to see if they checked it.

What we are looking for is a way to configure the overall approval.
For example, the overall approval/rejection does not change based on
any of the related approvals / rejections, but is set by the owner of
the work item.

An alternative would be to add a fourth alternative to the list of
Pending, Rejected, Approved such as Reviewed which only means you
have checked it and perhaps are waiting changes as described. Can
this be done?

I don't have any suggestions about how to change RTC to better fit your
desired process. (Not because I think it is impossible, but just
because I don't know how to do it.)

But I do have two suggestions about how you might tweak your process to
better fit RTC:

1. When an approver wants to suggest some changes but doesn't want to
reject the entire idea, he or she would leave the approval in the
Pending state and simply make comments in the work item. The fact that
the person has reviewed it is indicated by the comments in the work
item. A Reviewed state for an approval would be nice, but giving the
Pending state double duty can be made to work.

2. Teach people to not pay too much attention to the e-mail messages
about an approval being rejected. They should always use a pending
approvals query to find all of the approvals that need their attention.
If the owner of the work item decides that the objections are serious
enough that the whole idea should be dropped, then he or she should
delete anyone from the approval who still in a Pending state so they
don't waste time reviewing it further.

permanent link
Nigel Hopper (1032625) | answered Dec 24 '09, 3:07 a.m.
Hi David

I agree (and mention) that the scanning of comments is a possibility, but not a great one as with some things in review there can be many comments.

As to not teaching about the notice of e-mails, it is a possibility, but in reality enhancing RTC to not kill an item just because one person rejects it is the better solution!

Thanks, Nigel.

permanent link
Geoffrey Clemm (30.1k23035) | answered Dec 24 '09, 9:38 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note: Nigel has submitted work item 102241 for this.

MetaNote: When you do submit a work item for a forum discussion topic,
it is always best to post a message to the forum with the work item ID
as a followup to the message thread(if there is additional information
about the topic in the description of the new work item, I usually post
the description along with the work item ID, figuring that it makes the
message more interesting :-).

Cheers,
Geoff



NigelLH wrote:
Hi David

I agree (and mention) that the scanning of comments is a possibility,
but not a great one as with some things in review there can be many
comments.

As to not teaching about the notice of e-mails, it is a possibility,
but in reality enhancing RTC to not kill an item just because one
person rejects it is the better solution!

Thanks, Nigel.

Your answer


Register or to post your answer.