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

How to change the location of an issue from the backlog to the board using Jira API or automation?

Alex F_b9pra5

Here is the very important question. We use the next-gen project. I tried to switch to Kanplan and remembered why I did not like the backlog: you can have an issue that is done and at the same time it may still present in your backlog. I think this is an absolutely crazy situation. Atlassian engineers missed something.

I tried to find an action that can help to create an automation rule for fixing this, but there is no mention of backlog at all in Jira automation.

Then I decided to look for a field in the standart issues that is responsible for the issues location (backlog or board) to make a web request action that can call Jira API to change the value of the field, and did not find anything.

Is there any way to change the location of an issue from the backlog to the board and vice versa using Jira API or Jira automation?

Accepted answers

All comments

Ste Wright

Hi @Alex F

You're right that the backlog > board move is not status-based at this stage like it is in classic Jira projects.

There are a few things that Atlassian have added:

Issues in Done cannot be in the Backlog - if you move an issue to "Done" and refresh the board it will disappear. It doesn't show up in the last column though, it moves straight to hidden like those resolved >14 days ago do.
You can create an issue directly in a board column if required.

^ But I appreciate this doesn't solve the main issue. There are suggestions for this - I would vote / follow ideas such as JSWCLOUD-17471

As for automating this - I don't believe Automation for Jira works well with Next-Gen Boards at the moment. As for the REST API it's not something I've seen I'll be honest.

Ste

Alex F_b9pra5

Hi @Ste Wright,

Thank you for the answer.

You said that issues in Done cannot be in the backlog, but this is not so, just look at this screenshot:

Jira 1.png It was not by chance that I wrote about this in my question.

Yes, I know I can create an issue directly in a board, but I exactly want to use the backlog to prioritize and plan before issues get on the board.

I want to separately say thanks for the link to JSWCLOUD-17471. The fact is that I did not use classic projects and I did not know that "Backlog" may be an issue status. Yesterday I was visited by the idea that the ideal solution would be to create a separate predefined system status for issues: Backlog. Then issues in the backlog should have the Backlog status, if you change it to To do status, the issue should move from the backlog to the To do column of a board. This solves all problems, including automation!

*This status does not exist, the image was created in a graphical editor:

Jira 2.png

Today I planned to create such a feature request, but it turned out that it exists. However, I am very surprised that there are so few votes in the issue. I beleive that everyone who has issues with the backlog simply does not know about it or they do not know that Backlog may be an issue status.

And I should say that Jira automation works really well with next-gen projects, I have not faced any problem so far.

Aleš Jiránek

Hello, are there any news about this?

I would also like to set up automation or use backlog as issue status, but currently there is no option for this

Alex F_b9pra5

Hello, there is no news, but you can vote for this feature request JSWCLOUD-17471 to help move it further.

javmah

Try this :

request POST 'https://{jiraUserName}.atlassian.net/rest/agile/1.0/board/{boardID}/issue'

{

"issues": [

"{issue-key}"

]

}

Alex F_b9pra5

@javmah, this looks promising, thanks for that 👍

I have already switched from next-gen projects to classic projects because I'm tired of bugs, imperfections and missing functionality, now I have no problems.

If this question is still relevant for someone, see the detailed documentation for the specified method, it looks like it can move issues from the backlog to the board. It looks like it's a new method, I haven't found it before.

If anyone can confirm for sure that the method works, I'll close the question.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

rest-api

api

jira-cloud

addon-com.codebarrel.addons.automation

board

next-gen

automation

backlog