[FOLIO-3386] Github related changes are not displayed in JIRA Development section Created: 13/Jan/22 Updated: 10/Feb/22 Resolved: 10/Feb/22 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Aleh Litasau | Assignee: | David Crossley |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps sprint 132 |
| Development Team: | FOLIO DevOps |
| Description |
|
Overview: Changes made in scope of Jira tickets to folio-org-priv/folio-infrastructure are not displayed in Development sections Steps to Reproduce:
Expected Results: Commit is displayed in Development section Actual Results: Commit is not displayed in Development section **Additional Information: Potential issue is that repo is not integrated with Jira as repos in folio-org organizations. Kitfox team |
| Comments |
| Comment by David Crossley [ 19/Jan/22 ] |
|
Atlassian documentation: Link GitHub repositories with "Jira DVCS connector". |
| Comment by Wayne Schneider [ 07/Feb/22 ] |
|
John Malconian David needs a little help finding the correct password for the Github user folio-aws (assuming that's the right user). |
| Comment by David Crossley [ 09/Feb/22 ] |
|
We found the credentials for that user. Now in AWS Secrets Manager. |
| Comment by David Crossley [ 10/Feb/22 ] |
|
Done. Used "Jira DVCS" OAuth App and client secret via "folio-aws" user. |
| Comment by David Crossley [ 10/Feb/22 ] |
|
Note that people must use proper Jira issue identifier slugs, otherwise these GitHub links will not integrate, e.g. MODPERMS-XXXX (and it must be uppercase, and must contain the hyphen, with no spaces). Note that it can take 60+ minutes for Jira to collect those references from GitHub. Also improved documentation about Jira linking. |