You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This RFE covers expanding and leveraging the JIRA library to create a new JIRA ticket for every self-scheduling request and populating that into the API workflows for self-scheduling (SSM).
Purpose
This RFE covers expanding and leveraging the JIRA library to create a new JIRA ticket for every self-scheduling request and populating that into the API workflows for self-scheduling (SSM).
Configuration
Because there may be scenarios for new QUADS adopters that don't use JIRA, let's make this a configurable option (default being no) here https://github.com/redhat-performance/quads/blob/development/conf/selfservice.yml
We should also make ticket number an optional parameter otherwise but if this is turned on then it provides that value.
Format
We probably want to utilize a JIRA post jinja2 template for content.
Some ideas for JIRA Post submission:
(SSM) Cloud Description
where cloud description is taken from API requestrelated-to: #487
The text was updated successfully, but these errors were encountered: