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; } } }

Change Status when creating an issue

Lina Praškevičiūtė

When creating an issue I'd like to be able to edit starting Status so that I don't need to create an issue and then change status as a two-step process (which is slower). How can I achieve this?

Context: In our project, most of the issues that are created go to the backlog (workflow starts with status "New" which isn't shown in boards), but we also frequently create issues which should go to the board directly (status "Ready for development").

Accepted answers

Steven Behnke

It's not possible out of the box.

For my instance I have a listener that checks for a customfield value. If this customfield value (auto-close ticket) is present, the listener automatically fires the Close Issue transition.

It sounds like you'd want something similar.

Patrick Einheber

I've created https://jira.atlassian.com/browse/JRACLOUD-69559 for this.

All comments

Steven Behnke

It's not possible out of the box.

For my instance I have a listener that checks for a customfield value. If this customfield value (auto-close ticket) is present, the listener automatically fires the Close Issue transition.

It sounds like you'd want something similar.

unknown

Exactly as @Steven Behnke said. With Jira Service Desk you can use Automation to accomplish this.

Michael J Love

I edited my workflow so that the first status upon creation is "Backlog".

You need to copy your existing workflow. Edit it, and then assign the scheme to the issue types.

It will ask you to map statuses on any existing issues that use the status that is no longer in your workflow.

Michael J Love

Screen Shot 2018-03-09 at 6.26.31 AM.png

Michael J Love

Copy Workflow.png

unknown

Well @Michael J Love gave an obvious idea. You can make the transition available, but only use the transition that jump statuses when you need it!

You could also use a condition in that transition that avoid mistakes.

Patrick Einheber

I've created https://jira.atlassian.com/browse/JRACLOUD-69559 for this.

Admin Hustak

This needs to be added as an option. It's just a headache. These aren't solutions. They are work arounds,

Steven F Behnke

It's not really that complicated. Jira does not treat the Workflow/Status as a field. It's a complex arrangement of states, actions, conditions, validations, and other properties. Just 'setting' the status makes no sense whatsoever.

You should look into IssueService and the Workflow XML. It's pretty clear that the underlying Workflow Engine (OS Workflow) accepts and supports an Initial Action, which clearly Atlassian has mirrored into their model: https://docs.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/bc/issue/IssueService.html

For instance:

create(ApplicationUser user, IssueService.CreateValidationResult createValidationResult, String initialWorkflowActionName)

The IssueService::create method clearly has an argument `initialWorkflowActionName`. Presumably there's a method of modifying the Workflow XML to pass in this initialWorkflowActionName somehow. I would imagine that would give you what you're looking for, but that's just a guess on my part.

Sam Hatoum

not be complicated + a bunch of XML + a create() function is an oxymoron

I want to be able to create some tickets to go straight to the backlog, and other tickets to go straight into my "selected for development" column when I create that ticket. This is a UX problem and not a technical one.

Shawn_L_

This reply has been deleted.

Joris Vleminckx

People arriving to this place after googling, please go to the above ticket and "vote" for it (top right corner).

Artur Kornakov

Hi guys!
Found a workaround that's could be useful not only for me:
1. Create a checkbox custom field with the name 'Set the status' (or other) with option (e.g status Selected for development) and add it to the issue view.
You will see it on your 'create issue' window.

Actually you could make as many statuses as you want.

2. Create an trigger with condition and action in Jira Automation (it's free):
When: Issue created ->
If: Set the status is not empty (different if you created many statuses)
Then: Transition the status to 'Selected for development'

That's all, now if you select the status while the issue creation it will be automatically change the status.

But anyway hope that Jira developers will focus on that issue soon.

nick_w

I used the same field, but a different automation rule. The results are the same.

AndrewZ

I "fixed" this issue by changing my Jira usage habits. When I need to create new issue and start working on it instantly - I do following

add new issue
click on "popup message" and open issue page
set status to "In progress"

That's pretty logical, because I don't need to create few "In progress" issues and I need to open issue page anyway in order to add comments to it about progress etc.

Sarah Reed

How did you create the custom checkbox?

Max Howarth

Confirmed that this works as described!

Jason Wigle_1l1ele

I just want to agree with the consensus here.

I've been sent here by my producer because he, and other members of the team, find it to be a UX drag to create tickets and not be able to set them as "ready for development" or in our case "Not Started". (Same/Same)

I don't want to expose the team to the ENTIRE backlog on their Kanban board. Just the things that have been groomed and selected. And yes, sometimes we know they're selected as we make them.

It's Agile dev after all.

This is a UX issue and it should be as simple as selecting, somewhere, to add the status dropdown to the ticket creation window.

Joris Vleminckx

Update 2023: Atlassian has added this feature and has been rolling it out (amidst quite somo criticism) from users who didn't need the feature. ;-)

An example:
2023-03-23 17.07.58 whitestack.atlassian.net 1962333ab2a0.png

Joris Vleminckx

The feature now exists in Cloud!

Cf. https://community.atlassian.com/t5/Jira-questions/Change-Status-when-creating-an-issue/qaq-p/746730?utm_campaign=kudos_comment&utm_medium=email&utm_source=atlcomm&utm_content=topic

Gregory Martin_ih8y0p

Thanks for this information. Would you happen to know in which version of jira Data center this sub-feature has been released in? Thanks in advance for your help.

Karin Berg

Is this also already available in Jira Cloud? Because I do not have the option to set the initial Status.

Joris Vleminckx

@Kar My screenshot is related to the Cloud version.

Welcome!

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

Quick Links

Find more posts tagged with

jira

status