Skip to content
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

[RFE] Expand jira-workflow to post a closing message on completed requests #469

Closed
sadsfae opened this issue Mar 11, 2024 · 1 comment
Closed

Comments

@sadsfae
Copy link
Member

sadsfae commented Mar 11, 2024

This RFE covers adding the following functionality:

  • Modify https://github.com/redhat-performance/quads/blob/master/quads/tools/jira_workflow.py#L41 to do the following:

    • send an API post message to every issue that is being auto-closed by automation using a template like:

    https://github.com/redhat-performance/quads/tree/master/quads/templates/closing_message

    • send something like:

    We've detected there are no longer any running systems associated with this environment so we're closing this request. We hope your time in {{env_name}} was fruitful. Please remember to reference {{env_name}} and {{env_request_url}} for any results or documentation to spread awareness of this resource for other future tenants.

    We can can add two new configurable variables conf/quads.yml

    env_name:  "example lab"
    env_request_url: "https://example.com/requests"
@sadsfae sadsfae added this to the 2.0 Series - Bowie milestone Mar 11, 2024
@sadsfae sadsfae added this to To Do in 1.1 and 2.0 Series via automation Mar 11, 2024
@sadsfae
Copy link
Member Author

sadsfae commented Mar 11, 2024

Actually going to close this, you can do this within JIRA via their automation facility. No sense in carrying this burden for QUADS tools.

@sadsfae sadsfae closed this as completed Mar 11, 2024
1.1 and 2.0 Series automation moved this from To Do to Done Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant