Can we define proper workflows in this community, which different people/organizations will use at the same time?
Some kind of standard building plus consistency.
Welcome to the Atlassian Community!
No, we can't do this. Jira has a load of standard and simple workflows built into it, that it uses as a basis for a workflow for your new project when you create one. These are built to support the basic workflow for the type of project you are creating, but the whole point of them is to allow people to customise them to suit their needs.
The community can't tell us what a good "standard" workflow is for any given task much beyond "the defaults in Jira are pretty standard". You will need to talk to your users and standardise your workflows for your teams.
User definitely has the power to customize/build the workflows from scratch. (in addition) My idea was to build a couple of workflows as a template, which users can directly use OR also customize a little according to the business/use (don't go to build everything from scratch. which also helps the community to use similar workflows and support each other quickly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mmm, your users should not really have access to edit workflows. That should be up to your administrators to create standard shared workflows. It's unlikely your admins would need or want templates - they can copy existing workflows if someone needs to diverge.
For team-managed projects, where it's fine for project owners to amend workflows, there is no way to template anything - each workflow for each issue type is defaulted from the project template and has to be manually edited.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I find that the template or standard work-flows are a good place to start but it's not a one size fits all. They undoubtly need to be customized to fit the organzation and sometimes differnt for each project.
The bigest issue I have is the status of Pending- (None), or for no reason. This has become a place where ticekts go to be forgotten, as the SLA stops accruing time and they are no longer screaming for attention.
We have SLA- breach or about to breach alerts.
Is there any way to have a ticket automatically revert back to differnt status after a certain amount of time passing.
For example, if a ticket is "waiting on customer" for 48 hours, it reverts back to "waiting on support"?
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.