We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.

Cireson Portal should notify analysts if the work item they are working on has been modified

Jason_MeyerJason_Meyer Customer Adept IT Monkey ✭✭
Cireson Portal should notify analysts if the work item they are working on has been modified.

In our environment sometimes analysts are notified and they get the pop-up with bold text, the item has changed, and sometimes we do not.  I'm still trying to understand when it happens and more importantly, when it doesn't happen.

As an example,  a ticket is assigned to one analyst, they are working on it.  It gets assigned to someone else, original person still has it open and saves it.  The ticket is set back to the original person, all done without the original person knowing that someone else tried to assign that ticket.

Is this something unique on our configuration or is this a needed feature request?

Jason
1 votes

Submitted · Last Updated

Comments

  • Jeff_LangJeff_Lang Customer Advanced IT Monkey ✭✭✭
    @Jason_Meyer you could try something like this to prevent that from happening in the first place

  • Tom_HendricksTom_Hendricks Customer Super IT Monkey ✭✭✭✭✭
    I highly recommend @Jeff_Lang's suggestion, as well. 

    The data conflict error was causing a large number of our analysts to lose work before we implemented the work item lock and eliminated the conflict check (from the Admin Settings).  We tested beforehand to make sure that system/workflow updates would not get overwritten if an analyst saved an "older" iteration of the ticket from their browser, (loaded before the workflow ran, saved after) and everything went better than we expected.  Implementing the work item lock stopped a lot of hate mail.
Sign In or Register to comment.