locona / jira

Go client library/cli tool for Atlassian JIRA (jira cli tool)

jira cli

jira is a simple command line interface based on the jira module. The module uses the REST API to communicate with the Jira instance.

Go client library for Atlassian JIRA.

Feature

• Authentication (HTTP Basic).
• Create/Delete Issue.
• Batch Create/Delete Issue.
• Update issue transitions
• Update assignee.
• Integration Github.

Requirements

• Go
• Jira

Installation

go get -u github.com/locona/jira

DEMO Issue Create

DEMO Issue Delete

jira's Issues

jira auth: project not found

The automated release is failing 🚨

🚨 The automated release from the release/M11 branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release/M11 branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 1.5.0 on branch release/M11 cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.5.1 can be published from branch release/M11.

The following commits are responsible for the invalid release:

• Merge pull request #39 from locona/sample/skip-semantic-release (2505134)
• fix: sample skip semantic release. remove file (ffd8d57)
• fix (add file) (#36) (792e6c9)
• fix pull request #35 from locona/sample/skip-semantic-release (9c33ef5)
• fix: sample skip semantic release. add file (ecb2ff5)
• Merge pull request #33 from locona/master (6268bd7)
• fix(circleci) sample skip semantic release fix type (#32) (7e78cde)
• fix(circleci) sample skip semantic release fix type (028f1f4)
• Merge pull request #31 from locona/master (887f7be)
• Merge pull request #30 from locona/sample/skip-semantic-release (3848429)
• fix(circleci) sample skip semantic release (f516c54)
• sample skip semantic release (08cfcb7)
• chore(release): 1.5.0 [skip ci] (89bc15d)
• Merge branch 'release/M11' of github.com:locona/jira into release/M11 (2318d95)
• fix(circleci): regexp of branch. (ecd06f2)
• fix(circleci): regexp of branch. (7326611)
• fix: fix (fb4020c)
• chore(release): 1.5.0 [skip ci] (3e9a198)
• Merge branch 'release/M11' of github.com:locona/jira into release/M11 (eb5de4a)
• fix: fix (f3165c1)
• fix: fix (206ab8e)
• chore(release): 1.5.0 [skip ci] (6840062)
• fix: fix releaserc (dced623)
• fix: fix releaserc (364948d)
• Merge branch 'master' of github.com:locona/jira into release/M11 (2acd03b)
• fix: fix (9674f33)
• fix: fix (b6a8d1b)
• fix: fix (6ca6655)
• fix: fix (5eec11d)
• fix(semantic-release): patch version (c9a31ec)
• feat(semantic-release): channel false (e5cdfe9)
• chore(release): 1.4.0 [skip ci] (#28) (e17b597)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release/M11 with git revert or git reset.

A valid branch could be release/M10, release/M11 or release/M8.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the release/M3 branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release/M3 branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 1.1.1 on branch release/M3 cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.1.2 can be published from branch release/M3.

The following commits are responsible for the invalid release:

• fix(release): add file (60d8f58)
• fix(debug): add file (286be87)
• fix(circleci): remove dry-run (f2928d3)
• fix(circleci): fix (215c100)
• fix(debug): release (8ee7177)
• fix(circleci): fix (2c3b598)
• fix: semantic-release/git#119 (dca09c8)
• fix(file): add (6641ece)
• fix(debug): delete unused code. (bf69896)
• fix: fix (130eb5a)
• fix: update releaserc (d5bea0b)
• fix: upgrade (a4c2242)
• fix: fix (3a94b99)
• fix: fix Ci (42842d9)
• fix: fix (b71ef42)
• fix: fix CI (363e7f5)
• fix: filter only release branch (#19) (840234a)
• Merge branch 'master' of github.com:locona/jira (ec13db9)
• chore: ignore chore (d0e0e17)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release/M3 with git revert or git reset.

A valid branch could be release/M2 or release/M3.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the release/M8 branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the release/M8 branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 1.2.0 on branch release/M8 cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.2.4 can be published from branch release/M8.

The following commits are responsible for the invalid release:

• Merge branch 'master' of github.com:locona/jira (8d9da29)
• feat(release): first commit (80e76a9)
• fix: first commit (59cf649)
• fix: fix (7e9dbe4)
• fix: fix (4df9d2e)
• fix: fix (ce104dc)
• fix(channel): use master channel (3163438)
• fix(channel): update (3c611a0)
• improvement(channel): test (16dd6ac)
• feat: test for squash and merger (#23) (066ec69)
• fix: test squash and merge (#22) (8b6d1d2)
• improvement: release 1.1.17 (854b110)
• fix: release 1.1.16 (b56863e)
• fix: test (34df31f)
• fix(circleci): fix (751bbf0)
• improvement(circleci): update (4e265be)
• fix(circleci): use no-ci (c6a8f04)
• improvement: add (2063ad2)
• fix(semantic-release): bugfix (697e3b7)
• improvement(semantic-release): new file (76b855a)
• fix(semantic-release): update (69f34ec)
• fix(semantic-release): update configuration (5fde197)
• fix(semantic-release): fix (a5f1675)
• fix(semantic-release): update configuration (bf64f17)
• improvement(package): upgrade semantic-release (4336dfd)
• fix(semantic-release): update (4746c1a)
• fix(semantic-release): remove master (4203985)
• fix(semantic-release): add master branch (efe452e)
• improvement(semantic-release): update (4861cf3)
• chore(deps): bump npm from 6.13.3 to 6.13.4 (#20) (fcbf574)
• fix(debug): add debug to circleci (bfc7015)
• fix(bugfix): new Release (b417052)
• fix(release): add file (60d8f58)
• fix(debug): add file (286be87)
• fix(circleci): remove dry-run (f2928d3)
• fix(circleci): fix (215c100)
• fix(debug): release (8ee7177)
• fix(circleci): fix (2c3b598)
• fix: semantic-release/git#119 (dca09c8)
• fix(file): add (6641ece)
• fix(debug): delete unused code. (bf69896)
• fix: fix (130eb5a)
• fix: update releaserc (d5bea0b)
• fix: upgrade (a4c2242)
• fix: fix (3a94b99)
• fix: fix Ci (42842d9)
• fix: fix (b71ef42)
• fix: fix CI (363e7f5)
• fix: filter only release branch (#19) (840234a)
• Merge branch 'master' of github.com:locona/jira (ec13db9)
• chore: ignore chore (d0e0e17)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release/M8 with git revert or git reset.

A valid branch could be release/M7 or release/M8.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

QA: Staging/Production