Jira setup and status mapping

Status Mapping

Status mapping applies to both Jira and GitHub. Configure the local list and provider mapping together in .imdone/config.yml:

code:
  include_lists:
    - TODO
    - DOING
    - REVIEW
    - DONE
lists:
  - name: TODO
    hidden: false
    ignore: false
  - name: DOING
    hidden: false
    ignore: false
  - name: REVIEW
    hidden: false
    ignore: false
  - name: DONE
    hidden: false
    ignore: true
settings:
  plugins:
    JiraPlugin:
      providers:
        - jira
        - github
      statuses:
        - jira: To Do
          github: open
          list: TODO
        - jira: In Progress
          github: in_progress
          list: DOING
        - jira: Code Review
          github: code-review
          list: REVIEW
        - jira: Done
          github: closed
          list: DONE

Use the list value for the local imdone board column. Use jira for Jira workflow status names and github for GitHub states or workflow labels like code-review.

How the mapping is used:

• imdone pull reads provider state and chooses the local list. For GitHub, a configured workflow label/tag such as code-review wins before the normal open/closed fallback, and that label/tag is stored in local status metadata.
• imdone push reads the local list and updates provider state. Jira issues transition to the mapped Jira status. GitHub issues move to the mapped open/closed state or configured workflow label/tag, and stale configured workflow labels/tags are removed. Unmapped lists leave provider workflow state unchanged.

For Jira projects with custom workflows, exact workflow status names such as Code Review can map to their own local list before imdone falls back to the Jira status category. For GitHub projects, engineers can apply a label such as code-review when they want that workflow state reflected in the imdone list.