It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Change Status when creating an issue

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").

5 answers

2 accepted

2 votes
Answer accepted

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. 

2 votes

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

Well @Michael Pawlowsky 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.

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.

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

Steven Behnke Community Leader Jun 24, 2019

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. 

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. 

Like # people like this

This reply has been deleted.

Steven Behnke Community Leader Oct 18, 2019

Shawn, I don't think this question has anything to do with your issue.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

The add-in you’ve been waiting for: Jira Cloud for Excel 🙌

Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...

880 views 7 24
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you