+1

Trying to get team set up using Jira and this backlog is killing us. Why is this so difficult.

I stopped using Jira for a while (sounds like trying to quit an addiction) but here I am at a new job, stumbling on this old issue again. 

Please Atlassian, give this a bit of attention. 

Instead of typing +1, which nobody who is triaging tickets cares about, make sure you click on the [More] dropdown and select `Add Vote`, which increases the votes that can, hopefully, get someone at Atlassian to prioritize this.  The amount of clicks it takes to create an issue and put it on board is way too much.  Not everybody uses "strict scrum format"; when we get a high priority customer hotfix, we don't wait around for next sprint, we create a ticket, push code, and get it merged asap. The extra clicking and typing to create a ticket on our board is frankly silly.

Anyone who doesn't want tickets going straight to their board doesn't have to use whatever opt-in method is added to simplify things for those of us who do want to start work on a ticket immediately and have our board reflect what we are working on.

@Lukas why would you move from Linear to Jira?! Genuinely curious, not trolling.

We can chat on LinkedIn if you prefer, but I could not find you. I'm here.

We just completed a migration from Linear to Jira and i am already regretting it. How is this an unsolved issue?

It took 5 minutes of using Jira for this to become a glaringly obvious "SERIOUSLY?!?"-moment. people have warned me of jira, but i guess every kid has to put their hand on the stove.

pls fix

same here need this feature since it's so annoying of navigating to backlog, search backlog and drag and drop it.

I'm following this feature for a while and I must admit this lack of feature is a real pain. Especially that projects that are non-scrum have this capability. I mean like COMON DUDES, just roll this out to Scrum projects and all other types of projects. 

BUT ... IT'LL break the "strict scrum format" ... 

Who cares, just prompt us with a "are you sure ... this will modify sprint blablabla" 

You know what they say ?
Consultants that never managed a business dont know what they are talking about.

Well I guess the devs at Atlassian never really managed projects in real life.

Things change constantly.  

We need FLEXIBILITY. 

(edit : I tried loading images of the feature working on the kanban view of non-scrum projects)

This seems like an oversight, but it is a constant drag on the process of managing tickets, whereby a ticket can be written, assigned, and the kanban column defined, all from within the ticket view, but there is no way to add it to the board without navigating to the backlog, finding the ticket you just created, and then manually moving it to the board section.   This has caused delays, as PMs are creating tickets for projects and it is easy to forget or miss moving a ticket to the board, and then work has no way of progressing.
Worse still, there is no way to identify whether a ticket is on the board or not from the ticket view; searching for a ticket and viewing the info may show that the ticket status is "To Do", without it actually being displayed within that column on the board.

+1