[JSWCLOUD-18538] Jira ignores the Sprint state in JSON import

Type: Bug
Resolution: Not a bug
Priority: Low
Component/s: Classic - Board Configuration
Labels:
None

Support reference count:
1
Symptom Severity:
Severity 3 - Minor
Bug Fix Policy:
View Atlassian Cloud bug fix policy

This issue was simply a documentation inconsistency. The documentation has now been updated. "state" should be "FUTURE", "ACTIVE" or "CLOSED".

Issue Summary

Jira ignore the Sprint state in JSON file even though it has been set to "Complete"

Steps to Reproduce

Follow the steps as outlined here Importing data from JSON

Set the state of the sprint to "Complete" and make sure there is no existing Sprint with the same name.

          "priority" : "High",
          "description" : "Test JSON import",
          "status" : "DONE",
          "reporter" : "abcde-12345-fedcba",
          "issueType" : "Bug",
          "summary" : "Test JSON import",
          "customFieldValues": [
            {
              "fieldName": "Sprint",
              "fieldType": "com.pyxis.greenhopper.jira:gh-sprint",
              "value": [
                {
                  "rapidViewId": 11,
                  "state": "Complete",
                  "name": "SEK Sprint 123"

Import the json file using the External system import

Expected Results

Sprint is imported as "Complete Sprint" and not showing in backlog

Actual Results

Sprint is imported as "Future Sprint" and visible in backlog

Workaround

No workaround at this moment

Nigel Budd (CV) added a comment - 04/Nov/2019 10:39 AM

I'm still having problems with this.

Error returned from import...

Cannot add value [ [\{rapidViewId=12, state=CLOSED, name=Big New Sprint, startDate=2018-01-01, endDate=2018-01-01, completeDate=2018-01-01}] ] to CustomField Sprint in Issue with summary 'Test JSON import': null

any ideas?

Nigel Budd (CV) added a comment - 04/Nov/2019 10:39 AM I'm still having problems with this. Error returned from import... Cannot add value [ [\{rapidViewId=12, state=CLOSED, name=Big New Sprint, startDate=2018-01-01, endDate=2018-01-01, completeDate=2018-01-01}] ] to CustomField Sprint in Issue with summary 'Test JSON import': null any ideas?

Pedro Tacla Yamada made changes - 01/Nov/2019 12:45 AM

Resolution		New: Not a bug [ 12 ]
Status	Original: Long Term Backlog [ 12073 ]	New: Closed [ 6 ]

Pedro Tacla Yamada added a comment - 01/Nov/2019 12:45 AM

Closed as this was a documentation problem and the documentation has been updated at: https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html/

Pedro Tacla Yamada added a comment - 01/Nov/2019 12:45 AM Closed as this was a documentation problem and the documentation has been updated at: https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html/

Pedro Tacla Yamada added a comment - 01/Nov/2019 12:44 AM

Hello, this was a documentation issue.

The valid values for sprint state field in the JSON import are:

"CLOSED"
"ACTIVE"
"FUTURE"

When a sprint is "CLOSED" or "ACTIVE" it's also required that they have:

"startDate" - When this sprint started
"endDate" - When this sprint was planned to end

And "CLOSED" sprints also should provide:

"completeDate" - When this sprint actually ended

An example JSON is this:

{
  "projects": [
    {
      "name": "Project",
      "key": "KEY",
      "type": "software",
      "issues": [
        {
          "externalId": "1",
          "priority": "High",
          "description": "Sample 1",
          "reporter": "abcde-12345-fedcba",
          "issueType": "Bug",
          "summary": "Sample 1",
          "customFieldValues": [
            {
              "fieldName": "Sprint",
              "fieldType": "com.pyxis.greenhopper.jira:gh-sprint",
              "value": [
                {
                  "rapidViewId": 1,
                  "name": "Future sprint"
                }
              ]
            }
          ]
        },
        {
          "externalId": "2",
          "priority": "High",
          "description": "Sample 2",
          "reporter": "abcde-12345-fedcba",
          "issueType": "Bug",
          "summary": "Sample 2",
          "customFieldValues": [
            {
              "fieldName": "Sprint",
              "fieldType": "com.pyxis.greenhopper.jira:gh-sprint",
              "value": [
                {
                  "rapidViewId": 2,
                  "startDate": "2018-01-01",
                  "endDate": "2018-01-10",
                  "completeDate": "2018-01-10",
                  "state": "CLOSED",
                  "name": "Closed Sprint"
                }
              ]
            }
          ]
        }
      ]
    }
  ]
}

The documentation at https://confluence.atlassian.com/display/AdminJIRACloud/Importing+data+from+JSON has been updated with this information.

Pedro Tacla Yamada added a comment - 01/Nov/2019 12:44 AM Hello, this was a documentation issue. The valid values for sprint state field in the JSON import are: "CLOSED" "ACTIVE" "FUTURE" When a sprint is "CLOSED" or "ACTIVE" it's also required that they have: "startDate" - When this sprint started "endDate" - When this sprint was planned to end And "CLOSED" sprints also should provide: "completeDate" - When this sprint actually ended An example JSON is this: { "projects" : [ { "name" : "Project" , "key" : "KEY" , "type" : "software" , "issues" : [ { "externalId" : "1" , "priority" : "High" , "description" : "Sample 1" , "reporter" : "abcde-12345-fedcba" , "issueType" : "Bug" , "summary" : "Sample 1" , "customFieldValues" : [ { "fieldName" : "Sprint" , "fieldType" : "com.pyxis.greenhopper.jira:gh-sprint" , "value" : [ { "rapidViewId" : 1, "name" : "Future sprint" } ] } ] }, { "externalId" : "2" , "priority" : "High" , "description" : "Sample 2" , "reporter" : "abcde-12345-fedcba" , "issueType" : "Bug" , "summary" : "Sample 2" , "customFieldValues" : [ { "fieldName" : "Sprint" , "fieldType" : "com.pyxis.greenhopper.jira:gh-sprint" , "value" : [ { "rapidViewId" : 2, "startDate" : "2018-01-01" , "endDate" : "2018-01-10" , "completeDate" : "2018-01-10" , "state" : "CLOSED" , "name" : "Closed Sprint" } ] } ] } ] } ] } The documentation at https://confluence.atlassian.com/display/AdminJIRACloud/Importing+data+from+JSON has been updated with this information.

Pedro Tacla Yamada made changes - 01/Nov/2019 12:43 AM

Description

Original: h3. Issue Summary
Jira ignore the Sprint state in JSON file even though it has been set to "Complete"

h3. Steps to Reproduce
* Follow the steps as outlined here [Importing data from JSON|https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html/]
* Set the state of the sprint to "Complete" and make sure there is no existing Sprint with the same name.
{code}
          "priority" : "High",
          "description" : "Test JSON import",
          "status" : "DONE",
          "reporter" : "abcde-12345-fedcba",
          "issueType" : "Bug",
          "summary" : "Test JSON import",
          "customFieldValues": [
            {
              "fieldName": "Sprint",
              "fieldType": "com.pyxis.greenhopper.jira:gh-sprint",
              "value": [
                {
                  "rapidViewId": 11,
                  "state": "Complete",
                  "name": "SEK Sprint 123"
{code}
* Import the json file using the *External system import*

h3. Expected Results
Sprint is imported as "Complete Sprint" and not showing in backlog

h3. Actual Results
Sprint is imported as "Future Sprint" and visible in backlog

h3. Workaround
No workaround at this moment

New: _This issue was simply a documentation inconsistency. The documentation has now been updated. "state" should be "FUTURE", "ACTIVE" or "CLOSED"._
h3. Issue Summary

Jira ignore the Sprint state in JSON file even though it has been set to "Complete"
h3. Steps to Reproduce
* Follow the steps as outlined here [Importing data from JSON|https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html/]
* Set the state of the sprint to "Complete" and make sure there is no existing Sprint with the same name.
{code:java}
          "priority" : "High",
          "description" : "Test JSON import",
          "status" : "DONE",
          "reporter" : "abcde-12345-fedcba",
          "issueType" : "Bug",
          "summary" : "Test JSON import",
          "customFieldValues": [
            {
              "fieldName": "Sprint",
              "fieldType": "com.pyxis.greenhopper.jira:gh-sprint",
              "value": [
                {
                  "rapidViewId": 11,
                  "state": "Complete",
                  "name": "SEK Sprint 123"
{code}

* Import the json file using the *External system import*

h3. Expected Results

Sprint is imported as "Complete Sprint" and not showing in backlog
h3. Actual Results

Sprint is imported as "Future Sprint" and visible in backlog
h3. Workaround

No workaround at this moment

Pedro Tacla Yamada made changes - 31/Oct/2019 2:25 AM

Status

Original: Needs Triage [ 10030 ]

New: Long Term Backlog [ 12073 ]

Bugfix Automation Bot made changes - 29/Oct/2019 10:00 PM

Support reference count

New: 1

Adven made changes - 29/Oct/2019 3:50 PM

Summary

Original: Jira ignore the Sprint state in JSON file

New: Jira ignores the Sprint state in JSON import

Adven made changes - 29/Oct/2019 3:49 PM

Description

Original: h3. Issue Summary
Jira ignore the Sprint state in JSON file even though it has been set to "Complete"

h3. Steps to Reproduce
* Follow the steps as outlined here [Importing data from JSON|https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html/]
* Set the state of the sprint to "Complete"
{code}
          "priority" : "High",
          "description" : "Test JSON import",
          "status" : "DONE",
          "reporter" : "abcde-12345-fedcba",
          "issueType" : "Bug",
          "summary" : "Test JSON import",
          "customFieldValues": [
            {
              "fieldName": "Sprint",
              "fieldType": "com.pyxis.greenhopper.jira:gh-sprint",
              "value": [
                {
                  "rapidViewId": 11,
                  "state": "Complete",
                  "name": "SEK Sprint 123"
{code}
* Import the json file using the *External system import*

h3. Expected Results
Sprint is complete and not showing in backlog

h3. Actual Results
Sprint is still open and visible in backlog

h3. Workaround
No workaround at this moment

New: h3. Issue Summary
Jira ignore the Sprint state in JSON file even though it has been set to "Complete"

h3. Steps to Reproduce
* Follow the steps as outlined here [Importing data from JSON|https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html/]
* Set the state of the sprint to "Complete" and make sure there is no existing Sprint with the same name.
{code}
          "priority" : "High",
          "description" : "Test JSON import",
          "status" : "DONE",
          "reporter" : "abcde-12345-fedcba",
          "issueType" : "Bug",
          "summary" : "Test JSON import",
          "customFieldValues": [
            {
              "fieldName": "Sprint",
              "fieldType": "com.pyxis.greenhopper.jira:gh-sprint",
              "value": [
                {
                  "rapidViewId": 11,
                  "state": "Complete",
                  "name": "SEK Sprint 123"
{code}
* Import the json file using the *External system import*

h3. Expected Results
Sprint is imported as "Complete Sprint" and not showing in backlog

h3. Actual Results
Sprint is imported as "Future Sprint" and visible in backlog

h3. Workaround
No workaround at this moment

Azmir Zan (Inactive) created issue - 29/Oct/2019 3:47 PM

Assignee:: Unassigned

Reporter:: Azmir Zan (Inactive)

Affected customers:: 1 This affects my team

Watchers:: 4 Start watching this issue

Created:: 29/Oct/2019 3:47 PM

Updated:: 13/Feb/2020 2:50 AM

Resolved:: 01/Nov/2019 12:45 AM

Details

Description

Issue Summary

Steps to Reproduce

Expected Results

Actual Results

Workaround

Attachments

Forms

Activity

Collapse comment: Nigel Budd (CV) added a comment - 04/Nov/2019 10:39 AM

Expand comment: Nigel Budd (CV) added a comment - 04/Nov/2019 10:39 AM

Collapse comment: Pedro Tacla Yamada added a comment - 01/Nov/2019 12:45 AM

Expand comment: Pedro Tacla Yamada added a comment - 01/Nov/2019 12:45 AM

Collapse comment: Pedro Tacla Yamada added a comment - 01/Nov/2019 12:44 AM

Expand comment: Pedro Tacla Yamada added a comment - 01/Nov/2019 12:44 AM

People

Dates