I have two projects displayed on the same board. I would like the default status on one of the projects to be something other than 'Backlog' when entering a new issue. I'm fine with the other project defaulting to Backlog and going to the backlog. I just need the other project to bypass the backlog and default to 'In Progress'. Is there a way to do this and keep both projects on the same board?
This article explains how to change the status to which an issue is set during the Create Issue transition.
The initial status that the issue goes into at Create is dependent on the workflow. You would have to use two different workflows for the projects, one with a Create going to Backlog and the other going to a different status.
Then on the board, you just put both of those statuses in the Backlog - or just one.
Your filter for the board should include both projects. Something like:
Project in (ABC, DEF)
I am using a Next Gen project with I believe a Kanban board (not sure how to tell). The new issue/task is created in VS Code using the Jira Extension. When I create the new task it has the correct status but is only visible on the web view of our Jira account in the project's backlog, and not the board, unless I physically move it.
I think your problem is not the same as the original thread here, in that the original thread is for a user using a Classic project, and about modify the initial status of an issue during the Create transition. In her case Backlog was an issue status.
Since you are using a Next Gen project, Backlog is not an initial status but rather a separate attribute for the issue, which is either in the Backlog or moved to the Board. In both cases the Status of the issue can still be To Do.
You would determine if you're using a scrum board or kanban board by looking at the Project Settings > Features and seeing if Sprint feature is on (scrum board) or off (kanban board).
Assuming that you are using a Kanban board (Sprints feature is off) and you have turned the Backlog feature on, then there is a separate action to move an issue from the Backlog to the board. I'm afraid I don't know if that is accessible through the JIRA extension, as we don't create issues that way. Hopefully that gives you an additional clue in your search for an answer.
There are a few posts here about trying to use Automation to move the issues, but folks have been unsuccessful with that so far from the posts I've found.
Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....
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