User not able to create NEW Change Request if he already old change request created.

[Aryan]

Hi All,

We have a requirement where, we have to restrict user for not send their new changes for Request approval, they only have the rights to save the form in new state. If they already have a Change request created that's planned end date is passed the current date and time (A pop up message will display as "You already have a old change request created that's planned end date is passed , please close that change,")

So, first the requestor have to closed their old Change requests that are in scheduled /Implement/ review state and his planned end date is passed current date and time. Only then they are authorize to submit their new change for request approval. 

Can anyone help me on this.

Thank you

[Mark Manders]

I think this is a very user unfriendly solution. Why not just put logic on the old changes to chase them instead of setting it on the new ones? A change could very well miss being added to a CAB, because of this. 

I agree that users need to do the administration on their tickets, but that shouldn't prevent them from doing other work.

[Aryan]

Hi @Mark Manders ,

We already setup a reminder notifications to the folks to close their changes if the planned end date is passed but still we see that user are not closing their changes.

So we are going with this new method of restricting users to do not submit their new changes for the approval if they already have a existing changes that's planned end date is passed.