Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Import data to Jira specifying category different from default Backlog

hijapoos
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 26, 2020

Hi All,

 

We have some (working) json code made by clever predecessors to push tickets into Jira, here it is:

 

{

    "fields": {

        "project":

        {

          "key" : "{{$jiraproject}}"

        },

        "summary" : "{{$summary}}",

        "description" : "{{$description}}",

        "issuetype": { "name" : "Development" },

        "customfield_10025" : {

          "value": "{{$client}}"

        },

        @IF(!empty($due_date))

        "duedate" : "{{$due_date}}",

        @endif

        "customfield_10029" : {{$total}},

        "customfield_11500" : {{$dev_hours}}

    }

}

 

I have been asked to update this with a new line so that the Destination Step is “CS Specification” instead of the default “Backlog”.

Two questions:

  1. Backlog is the default on the system and we are not changing that, however is it possible to import data as above which can instead start with status of CS Specification?
  2. Can this be done via a customfield? If so how can I find which custom field is used for Backlog etc. 

 

Thanks

Tim

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Champion
August 26, 2020

If you are using the REST API, the answer is no. The issue must follow the workflow and so will be created in with the initial status of the applicable issue workflow.

You could use code to change the status after the issue is created, though.

hijapoos
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 27, 2020

Thanks Trudy, this is a logical solution to the issue.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events