Prevent the requester to appove the CMR

[Himanshu Bansal]

Is it possible to Prevent the requester of a change to appove the CMR.

In other words, the reporter/requester shall not be able to approve the CMR by himself. 

[Vishal]

Hi @Himanshu Bansal 

You can do it other way around, meaning set list of approvers. You can use user condition in the workflow transition to prevent users from approving if they are not the part of specified condition. 

Hope this clarifies.

[Himanshu Bansal]

Thanks for a quick turnaround Vishal.

It would be great if you could outline the steps to achieve the same 

[Vishal]

Hi @Himanshu Bansal 

Check this article, its a step by step guide to advance workflow configuration.

[Himanshu Bansal]

@Vishal - Thanks for your correspondence.

Another part where I find myself stuck is.. Can we have multi-level approvals.

The assignee group be the first to approve and then CAB.

[Vishal]

Hi @Himanshu Bansal 

You'll have to create multiple statuses for example Approval 1 > CAB Approval > Approval 2 > Approval 3, something like this. And as mentioned above, at each transition you'll have to set respective list of users as approvers in the condition. So that no users except the listed will be able to transition the issues from particular status.

[Himanshu Bansal]

@Vishal - Thanks yet again.

One last query. I have recently added a few custom fields in CMR project. However, if I clone an old one, it does not ask for the newer fields to be populated..

Is it default behavior or can it be managed as well. ?

Kindly help

[Vishal]

Hi @Himanshu Bansal 

Yes, it is default behavior, it wont ask you to fill the newly created fields, it will only throw error if at all those new fields are mandatory.

Hope this helps.

[Himanshu Bansal]

@Vishal - All those fields are mandatory. Lemme re-visit the instance to figure out what's wrong.