Inquiry on Sprint Health Gadget

[Tristen John Bagain]

Hi,

Need to understand the algorithm used in the yellow section on the sprint health gadget. Is it based off the difference between Original Estimate and Time Remaining?

This page https://confluence.atlassian.com/agile064/jira-agile-user-s-guide/using-the-jira-agile-gadgets/using-the-sprint-health-gadget doesn't explain that part.

[Alexey Matveev]

Hello,

You should use the POST /rest/api/2/issue/bulk endpoint:

https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/?_ga=2.15474545.675557620.1538152808-65270402.1526147845#api/2/issue-createIssues

[Tim Cares]

Thank you, I didn't know about that endpoint. But now I'm getting this error:

{"errorMessages":["No issue data was provided by request"],"errors":{}}

I confirmed that I have valid json in my file.

[Alexey Matveev]

How did you confirm that you have a valid Json? Jira says there is no issue data.

[Tim Cares]

I just dumped the data into an online validator tool (I used https://jsonlint.com/). In any case, I was able to do this a different way by using the original issue endpoint and then just iterating over each JSON object and creating issues one by one.

[Alexey Matveev]

If you validated a json, it does not mean that it will work. It must be of the required structure and your json is not.

[Tim Cares]

Okay, well,l as I noted, I rewrote my code so that it just feeds one JSON object at a time to the issue endpoint and that worked, so still not sure why the bulk endpoint did not. At this point, I can close this topic.

[Nil Ister]

If you're using Python and Requests library following might be helpful.

In your post request don't forget to give data attribute the issues in json format

url='https://www.random.com'
data=json.dumps(all_issues)
headers={'Content-Type': 'application/json'}

response = requests.post(url, data=data, headers=headers)

[Chris Burgdorff]

I'm getting the same:
No issue data was provided by request

And I'm like 90% sure the req body is formatted right, according to those docs. Is this just an outdated endpoint?

I could do what Tim did and just iterate through them, but that's not a great solution if you have a lot of issues to create.

[Chris Burgdorff]

Nevermind. I got it working!

All the fields besides update are subdfields of "fields". Here is my working code:

const issuesToCreate: {

  update: object;

  fields: { project: { id: number },

  summary: string,

  issuetype: { id: number },

  description: string,

  assignee?: { name: string } | null,

}}[] = [];

actionItems.forEach((actionItem: ActionItem) => {

  issuesToCreate.push({

    update: {},

    fields: { project: { id: project.id} ,

    summary: actionItem.title,

    description: actionItem.actionItem,

    issuetype: { id: selectedIssueType.id },

    ...(actionItem.responsibleParty ? {

      assignee: {

        name: actionItem.responsibleParty

      }

    } : {})

  }})

});

// Post to the bulk create API route to create the actual issues on Jira

const issueCreateResponse = await fetch(`https://${integration.Domain}/rest/api/2/issue/bulk`, {

  method: "POST",

  headers: {

    "Content-Type": "application/json",

    "Accept": "application/json",

    "Authorization": authHeader

  },

  body: JSON.stringify({issueUpdates: issuesToCreate}),

});