[RFE] auto-resolve extension requests

[kambiz-aghaiepour]

Once an extension request has been logged, it would be nice to be able to run the quads CLI with something like:

quads --extend --cloud cloudXX --weeks YY --extend-ticket ZZZZ

The above would operate as expected and use the JIRA API to log the extension message in the ticket and mark it as completed.

[sadsfae]

Once an extension request has been logged, it would be nice to be able to run the quads CLI with something like:

quads --extend --cloud cloudXX --weeks YY --extend-ticket ZZZZ

The above would operate as expected and use the JIRA API to log the extension message in the ticket and mark it as completed.

Nice feature, @kambiz-aghaiepour --extend-ticket should be an optional value as not all QUADS adopters will use JIRA but I dig it.

One thing to consider is there is no ownership of the ticket in this process, and no way for QUADS to know who to assign it to to accrue story points. Therefore you should pass the owner to assign the ticket to before resolving it that should match their JIRA username.

Alternatively and perhaps better is to auto-assign these tickets to the perfscale-api user (and have jira_automation_user as a var for example). Nobody cares about actual per-user story point allotment nor is it even a useful metric, but it's important to have all completed extension tickets assigned to someone or we get weird skews in our JIRA reporting and a growing list of unowned tickets which skews actual, useful metrics about how busy the project is.