We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.83
    • 10.79
    • REST API
    • None
    • 1
    • Severity 3 - Minor

      Issue Summary

      When creating an RV using API 2.0, users can't easily figure out the right status and health because there is a logic behind the health field and it's dependent on the selected state.

      Steps to Reproduce

      1. Create an RV via API and set the necessary required fields. Purposely set the status to 1 and health to 3.
      2. Observe the result

      Expected Results

      To help reduce this error, status and health should not be required via API and should have a default value like when we create it in the GUI.

      Actual Results

      Cannot create Release Vehicle. Value for health is invalid.

      Workaround

      Users have to be aware of the following combination when creating RV via API

                  Status:
                   * 1 = planning     - health:2,4,5
                   * 2 = in progress  - health:2,3,4,5
                   * 3 = launched     - health:2,3,4,5
                   * 4 = closed       - health:1
                   * 5 = canceled     - health:1
                   * 6 = archived     - health:1
      
                   Health:
                   * 1 = Complete
                   * 2 = At Risk
                   * 3 = Critical / Slip
                   * 4 = On Track
                   * 5 = On Hold
      

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Icon: Bug Bug
              • Resolution: Fixed
              • Icon: Low Low
              • 10.83
              • 10.79
              • REST API
              • None
              • 1
              • Severity 3 - Minor

                Issue Summary

                When creating an RV using API 2.0, users can't easily figure out the right status and health because there is a logic behind the health field and it's dependent on the selected state.

                Steps to Reproduce

                1. Create an RV via API and set the necessary required fields. Purposely set the status to 1 and health to 3.
                2. Observe the result

                Expected Results

                To help reduce this error, status and health should not be required via API and should have a default value like when we create it in the GUI.

                Actual Results

                Cannot create Release Vehicle. Value for health is invalid.

                Workaround

                Users have to be aware of the following combination when creating RV via API

                            Status:
                             * 1 = planning     - health:2,4,5
                             * 2 = in progress  - health:2,3,4,5
                             * 3 = launched     - health:2,3,4,5
                             * 4 = closed       - health:1
                             * 5 = canceled     - health:1
                             * 6 = archived     - health:1
                
                             Health:
                             * 1 = Complete
                             * 2 = At Risk
                             * 3 = Critical / Slip
                             * 4 = On Track
                             * 5 = On Hold
                

                        kforeman@atlassian.com Kyle Foreman
                        lsoronio@atlassian.com Leo Soronio
                        Affected customers:
                        1 This affects my team
                        Watchers:
                        5 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            kforeman@atlassian.com Kyle Foreman
                            lsoronio@atlassian.com Leo Soronio
                            Affected customers:
                            1 Vote for this issue
                            Watchers:
                            5 Start watching this issue

                              Created:
                              Updated:
                              Resolved: