Skip to content

[skip changelog] Add workflow to mirror issue on Jira to ease grooming #851

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 23, 2020

Conversation

silvanocerza
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The PR has no duplicates (please search among the Pull Requests
    before creating one)
  • The PR follows our contributing guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce?
    Whenever a new issue is created in this repository this new workflow is triggered, it creates a new issue on Jira with the same content as the GH one and add labels to both. This is done to ease grooming of new issues.
  • What is the current behavior?
    Newly created issues on Github are processed manully.
  • What is the new behavior?
    Newly created issues on Github are mirrored on Jira to ease grooming.
  • Does this PR introduce a breaking change?
    No.
  • Other information:
    None.

See how to contribute

@silvanocerza silvanocerza requested review from per1234 and umbynos July 23, 2020 09:33
@silvanocerza silvanocerza self-assigned this Jul 23, 2020
@silvanocerza silvanocerza force-pushed the scerza/issues-grooming branch from b36f24c to 1952605 Compare July 23, 2020 09:35
--noedit \
-e ${{ secrets.JIRA_BASE_URL }} \
-u ${{ secrets.JIRA_USER_EMAIL }} \
-p ATL -i Task \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it's better to place the project name in the secrets?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, done.

@silvanocerza silvanocerza force-pushed the scerza/issues-grooming branch from 1952605 to 9005fdb Compare July 23, 2020 09:47
@silvanocerza silvanocerza force-pushed the scerza/issues-grooming branch from 9005fdb to 342c429 Compare July 23, 2020 09:48
Copy link
Contributor

@umbynos umbynos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@silvanocerza silvanocerza merged commit 54c7b1f into master Jul 23, 2020
@silvanocerza silvanocerza deleted the scerza/issues-grooming branch July 23, 2020 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants