Closed ennioma closed 2 years ago
orbs: jira: circleci/jira@1.3.0
I've a pipeline which is triggered when something is merged to develop.
When it happens we trigger a new workflow which tags a new version of our software.
As you can see, the flow is triggered on a specific tag.
And the jira_notify job is executed here:
That release include only one ticket which has been merged to develop, i.e. it's ABC-123 and that ticket name is included:
This is the yml chunk where I've configured jira_notify:
- base_checkout: name: Prod deploy post-steps: - jira/notify: environment_type: production job_type: deployment scan_commit_body: false
I've tried with both scan_commit_body = true and false.
The ticket ABC-123 is marked as deployed on JIRA
Actually if I enable scan_commit_body: true I get
Though this appears to have come first, there is more conversation in #58 which appears to be a dupe. Closing this issue in favor of the dupe, #58
Orb version
orbs: jira: circleci/jira@1.3.0
What happened
I've a pipeline which is triggered when something is merged to develop.
When it happens we trigger a new workflow which tags a new version of our software.
As you can see, the flow is triggered on a specific tag.
And the jira_notify job is executed here:
That release include only one ticket which has been merged to develop, i.e. it's ABC-123 and that ticket name is included:
This is the yml chunk where I've configured jira_notify:
I've tried with both scan_commit_body = true and false.
Expected behavior
The ticket ABC-123 is marked as deployed on JIRA
Actual behavior