Skip to content
This repository has been archived by the owner on Dec 9, 2023. It is now read-only.

Handle case where dynamic Jira project properties are modified upstream #22

Closed
mafrosis opened this issue Apr 12, 2020 · 1 comment
Closed
Milestone

Comments

@mafrosis
Copy link
Owner

When issues are created/edited offline, they model the current priorities/issuetypes based on how the Jira project was configured at the last sync.

If these change whilst we have un-sync'd issues locally, then bad things will happen (your local data will be broken).

For example:

  1. a project may have Lowest, Low, Medium, High as priorities for the Story issuetype
  2. modify a Story-type issue to have priority = Lowest
  3. update the project on Jira to have only Low, Medium, High as priorities for the Story issuetype
  4. run jiracli push
  5. I expect an API error here 😄
@mafrosis mafrosis added this to the 0.2.6 milestone Aug 10, 2021
@mafrosis
Copy link
Owner Author

Closing as not actually a problem. The API will report an invalid priority (or other list value) on push, so that it can be corrected offline

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant