Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-7147

Adding a program on a theme via API results in 'Cannot update theme with id #. Value for release is invalid.' error.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 11.13.0
    • 10.133.3
    • Themes
    • 2
    • Severity 3 - Minor
    • No
    • None

      Issue Summary

      Currently there's a difference in behavior between the UI and the API in Themes. In the UI, a user can add a program to a theme at any time, regardless of if that program is associated with a PI that's tied to the Theme or not. There is a warning when a program is not assigned to one or more of PI, but you can add any program at any time if desired.

      In the API, you can only add a program to a theme if at least one program is associated to each PI on the theme. Once each PI has at least one program, you can then add any other program to the theme.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Select a theme without Programs or PIs.
      2. Add a program.
      3. Add one or more PI.
      4. Remove the program.
      5. Attempt to add a program that doesn't belong to the PI via API.

      Expected Results

      The program is added to the Theme. Optionally, a warning is displayed notifying the user that one or more PI are not assigned to the added program.

      Actual Results

      Program is not added, and the following error is displayed: 'Cannot update theme with id #. Value for release is invalid.'

      Example of error in API:

      Example of warning in UI:

      Workaround

      Using the UI instead of the API to add at least one program associated with each Program Increment will allow you to use the API to add the rest of the programs to a theme.

              9cd547254f0d Vishnuvardhan Vaidhyanathan
              4359d07f7f4f Christopher Stringari
              Votes:
              8 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: