nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to design Workflow for this attached requirement.

Paras Sachan

Please check Image file.

Accepted answers

Ismael Jimoh

Hi @Paras Sachan

create all statuses an issue will pass through and create the necessary transitions
where you have if/else or yes/no checks, you can use a condition or validator to check your values before the transition is made (with conditions the transition will not appear at all while a validator check field value when performing the transition)
use the field required validator to check if a field value is set or not.
For the urgency you may need to write a script with scriptrunner add on to do the comparison and assign the correct value and this may apply to other fields you may have as well. These should go into post function section of the transition.
You can also use automation within the project settings to perform checks and when your check is met, perform the next subsequent action automatically (for example is it a major incident, if you have a field users state what type of incident it is, you can use this to automatically transition the issue to the destination status)

These are the things I will look at when creating what you shared in the image.

All comments

Ismael Jimoh

Hi @Paras Sachan

create all statuses an issue will pass through and create the necessary transitions
where you have if/else or yes/no checks, you can use a condition or validator to check your values before the transition is made (with conditions the transition will not appear at all while a validator check field value when performing the transition)
use the field required validator to check if a field value is set or not.
For the urgency you may need to write a script with scriptrunner add on to do the comparison and assign the correct value and this may apply to other fields you may have as well. These should go into post function section of the transition.
You can also use automation within the project settings to perform checks and when your check is met, perform the next subsequent action automatically (for example is it a major incident, if you have a field users state what type of incident it is, you can use this to automatically transition the issue to the destination status)

These are the things I will look at when creating what you shared in the image.

Paras Sachan

Please clear which is TO-DO status , which is IN-Progress status and which one is Done status.

How to classify?

Ismael Jimoh

Hi @Paras Sachan

To do statuses are the statuses your ticket starts from the instant they are created,
In Progress statuses are statuses between To Do and Done Status. Here various tasks are performed on the ticket to enable getting it to the done status
Done statuses are statuses signifying that for the ticket all planned work is done and completed.

Regards.

Ismael Jimoh

Consider reading more about Workflows here: https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-statuses-priorities-and-resolutions/

I will also recommend considering an Atlassian training or getting a consultant if you need help as this impacts your usage and this knowledge is needed for the fundamentals of getting the application to work as you intend it to.

Natalie Chapman

I agree there are many templates that you can use for your design and not reinvent the wheel.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

atl-gruland

jira-service-management-cloud

jira-service-management