You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Rebecca Morris , welcome to the community.
The column that a newly Created issue appears in is driven by the initial workflow status associated with the create action. If you look at your workflow, this will become obvious. The statuses of your workflow map to your board columns under board settings. Generally speaking, if you have a backlog status, and that is your initial status, then you want newly created issues to show up in your backlog. This allows you to manage your backlog and decide which issues are moved into the kanban or scrum board to be worked on. Now to your specific issue, it seems that you have backlog and a new Statuses. Both of these appear to me to be an initial status and maybe you don't need both? Could you please share a screenshot of your workflow and describe more specifically what you would like that workflow look like?
OK so if you want New Ticket to be the initial status then you need to change your workflow such that the Create transition goes to New Ticket. Now, the question is where do you want New Ticket and Backlog issues to appear on your board? Do you want both to appear in the Backlog or do you want one of them to appear in the main kanban view, or maybe you don't want New Ticket to be map to any column? In any event, whatever your requirement is, you want to edit the board settings in the columns view and map the statuses as you wish them to appear on your boards.
One final, and likely obvious note, regarding changing the workflow do you want to ensure that this is not a sheared workflow otherwise you will be impacting other projects.
So if you want to make this change, then you're going to want to make a copy of the workflow and edit it and then re-associate this new workflow. Please note this will move you out of software, simplified workflow, which may not be what you want. You can always try it and then revert back to the previous workflow.
with everything we have discussed here, I would rewind a bit and ask myself why I am choosing to make this change. It is a bit abnormal, IMO. Looking at all of the statuses that you have leads me to believe that the workflow is more complex than maybe it needs to be. The fact that you have five different "to do" statuses is a bit of a flag for me.
No apologies necessary. I would suggest chatting with your Org admin to help you with this. By doing so, you will be able to discuss with them the details of what your team needs and the admin can consider what the best option is and help you solve your needs.