Some JIRA Automation #473
Some JIRA Automation #473
Conversation
for creating the ticket. A sprint is a custom field; figure out.
coverbeck
force-pushed
the
feature/jira_automation
branch
from
371c3e3 to
3a72784
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## develop #473 +/- ##
==========================================
Coverage 42.64% 42.64%
Complexity 172 172
==========================================
Files 24 24
Lines 1597 1597
Branches 131 131
==========================================
Hits 681 681
Misses 878 878
Partials 38 38
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
coverbeck
changed the title
jira_automation/README.md
Outdated
| Unito was seemingly mysteriously closing JIRA issues at random. It turned out to be because we hadn't properly configured | ||
| a GitHub and JIRA user in Unito -- it's the Unito intended behavior. We currently don't need to run this, although if we have | ||
| a configuration issue again, it could be useful in the future. | ||
| 2. io.dockstore.jira.MilestoneChecker - generates GitHub and JQL queries to find mismatches in the JIRA fix version and GitHub milestone. The JIRA fix version is |
There was a problem hiding this comment.
i.e. this is still a common problem
There was a problem hiding this comment.
i.e. this is still a common problem
The Milestone thing is a common problem; I typically run it before a backlog grooming meeting and it will usually find a couple of issues out of sync.
Hopefully we won't need the ResolutionChecker again, since we figured out how the cause. But I wanted to keep it in case we onboard somebody incorrectly in the future and it crops up, and we need to go find the issues that were incorrectly closed.
There was a problem hiding this comment.
(Sorry, comment wasn't a question. Rather, I meant since this is a common problem, this should probably be re-ordered to be first)
jira_automation/pom.xml
Outdated
| <revision>1.0</revision> | ||
| <changelist>.0-SNAPSHOT</changelist> | ||
|
|
||
| <!-- |
There was a problem hiding this comment.
these seem unused (swagger, openapi annotations)
|
SonarCloud Quality Gate failed.
|
Description
This has been in a branch for several months now; I want to merge it so it's not lost even though some of it is in progress. I wouldn't submit a PR of this quality for the web service, but I think it's acceptable for support. But I can tidy up more if we think it's worth it.
This is some code to help with the JIRA admin tasks:
Review Instructions
Try running the MilestoneChecker. You'll probably need a GitHub token, although it may work once or twice without a GitHub token. You can just run it in the IDE:
It should output a JIRA url in the console.
Issue
No issue was created.
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!
mvn clean installin the project that you have modified (until https://ucsc-cgl.atlassian.net/browse/SEAB-5300 adds multi-module support properly)