I'm trying to figure out how to change the workflow of Servicedesk to meet our needs. The problem I encounter is that I cannot find any instructions how to make more statuses for the customer to see. The only 2 that are "enabled" are 'Waiting for support' and 'Waiting for customer'.
I want to have more statuses like:
Is this possible? I know how to change the workflow etc but don't seem to be able to do this.
Thank you in advance.
in my experience, alle statuses are visible for the customers.
You can add or rename statuses in the workflow scheme for your project. Double click on a status gives you the possibility to change the name. There should be a few button to Add existing status or Add new status.
What the customers see in the portal can even be modified in the Customer portal settings. When you make a request type, in de edit form screen, there is a second tab: workflow statuses. There you change the final displayed status. This is very useful when making a workflow with multiple statuses for internal use (like 'on hold', 'in progress', ..) Customers don't need to see them all because it easily gets confusing. If you change the 'status name shown to customer' for 'in progress' and 'on hold' to 'Your request is in development', no change in status is shown for the customer when the actual status changes between 'in progress' and 'on hold'.
hope this makes sense
In this issue (https://answers.atlassian.com/questions/306326) there is a discussion about the triggers that are build in on the workflow of servicedesk. It seems rather complicated to be able to make a status or transition which will work correctly. If you edit the Servicedesk workflow and select one of the transitions or the one of the statuses you will notice that they have properties, validators and post functions. These are the ones which are needed to sent notifications and to trigger changes of statuses.
I also tried to figure out how these work or find some kind of documentation on them but can't find it. This makes it very hard to do anything with the workflow besides adding statuses which are not visible to the customer.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs