• 0 Vote(s) - 0 Average
  • 5
  • 4
  • 3
  • 2
  • 1
Thread Modes

Initial status of tickets
#1
Hi,

We are using heavily quick call form for entering tickets. 

All tickets (submited or not) have status "In progress" which is something that we would like to change.

I've tried to find this paremeter in:
Default valued
Other paramters

But no luck.

Problem is that "In progress" is used for filtering stuff that we are acctually working on, and when something is not in a workflow correct status would be "New" or something like that.

Please help me!

Regards,
Dok
doktabar, proud to be a member of EV CONNECT FORUM since Nov 2015.

#2
We ran into the same issue and were not able to find a way to set Input Errors and Drafts to the "New" status.  We ended up excluding them from our reports/filters by adding the following SQL code to our queries:

Code:
SD_REQUEST.REQUEST_ID NOT IN
(
    SELECT    SD_REQUEST.REQUEST_ID
    FROM    SD_REQUEST
            INNER JOIN AM_ACTION ON SD_REQUEST.REQUEST_ID = AM_ACTION.REQUEST_ID
            INNER JOIN AM_ACTION_TYPE ON AM_ACTION_TYPE.ACTION_TYPE_ID = AM_ACTION.ACTION_TYPE_ID
    WHERE    (AM_ACTION_TYPE.ACTION_TYPE_GUID = '{2502C70E-D9A6-4662-AE2E-B15DA75CA763}' OR AM_ACTION_TYPE.ACTION_TYPE_GUID = '{0C654867-7C28-43A5-AF3C-C797220A8D27}')
            AND AM_ACTION.END_DATE_UT IS NULL
)
Sarah Schumacher
Service Desk Tool Administrator

#3
It would be easiest if the default could be changed. Does not seem to be an option.

It's not ideal, but another option might be to NOT use "in progress" for your work or in any workflows. Use something else like "working" or "work in progress" (a new status). This way you know that if it says "in progress" it's a system state until the workflow kicks in and uses one of your new workflow statuses. 

Of course this would require updating all existing workflow steps that use the ootb "in progress" status to your new status.
Jack Reeder
FMX Solutions Inc.
Jack.Reeder@fmxsolutions.com

#4
Thanks FMX and sarah.

First thing it's been already done and are doing it that way.
The FMX solution is also my ultimate solution - but wanted to check first if I'm missing something. As it clearly looks forme very unsusuall to offer "out of the box" status "New" and "In progress" - and then hardcode the very first status as "In progress". If hardcode something - than use something that is correctly representing status "New", "Open", "Input", "inpute error" - whatever. As "New" already created (out of the box) - why not hardcode it?

Implementing new status "In progress" instead of old one in every workflow step (more than 20 wf), every report, filter, business rule and so on - seems like major change for something that should be as such in very beginning. Renaming is possible - so this could save some time, but loads of filters relay on GUID mark not on string value.
Doing it - will definatelly cost some time.

Thanks!
doktabar, proud to be a member of EV CONNECT FORUM since Nov 2015.






Users browsing this thread: 1 Guest(s)