Implement transition stats for the jira plugin

[lukaszachy]

Should I make it more generic? As in 'JiraTransitioned' ? In theory one could have config with one project counting 'Release Pending' and another where 'Integration' is counted as the user's role is different

Config like

[jira-where-developer]
project = DEVEL
transition_state = 'Integration'

[jira-where-qe]
project = QE
transition_state = 'Release Pending'

Seems that states and workflows can be too different

[psss]

Thanks for the improvement! The custom verified_status field looks good to me. Works nicely, I only ran into a problem when login contained @. Should be fixed by d339504.

[psss]

For reference, the reported error was:

Failed to fetch jira issues for query 'status changed to 'Release Pending' and status changed by psplicha@redhat.com after 2024-01-08 before 2024-01-15'.
The reason was 'Bad Request' and the error was 'Error in the JQL Query: The character '@' is a reserved JQL character. You must enclose it in a string or use the escape '\u0040' instead. (line 1, character 67)'.

[jharuda]

@lukaszachy Your implementation makes sense, generally speaking. How about specifying important states by list variable in the config? I am just thinking how to make it more general for different Jira projects.

The idea of this issue #364 is to have for example something like this in the config:

[jira]
...
states=['Release pedning', 'In progress']
...

Default (without states variable in the config) behavior can be the same as it is now, which means generating only updates section to hide different states in the did output.

[psss]

List of interesting statuses sounds nice, it would give even a bit more flexibility to the user.

[lukaszachy]

Or like project in (PROJECT_NAME) AND "QA Contact" in (USER_NAME) AND status changed to ("Release Pending") during ("2024/05/13", "2024/05/17").

I guess I should update PR.

[sandrobonazzola]

Can you please rebase?

[sandrobonazzola]

pre-commit is failing on:

************* Module did.plugins.jira
did/plugins/jira.py:419:12: C0209: Formatting a regular string which could be an f-string (consider-using-f-string)
did/plugins/jira.py:426:28: C0209: Formatting a regular string which could be an f-string (consider-using-f-string)
did/plugins/jira.py:574:21: C0209: Formatting a regular string which could be an f-string (consider-using-f-string)

[psss]

pre-commit is failing on:

Fixed in ef08f17.

[psss]

Or like project in (PROJECT_NAME) AND "QA Contact" in (USER_NAME) AND status changed to ("Release Pending") during ("2024/05/13", "2024/05/17").

This sounds very nicely flexible!

I guess I should update PR.

I'd rather suggest to handle this in a separate pull request. We could have both target status (for basic use cases) and transition query (for more complex ones).

In order to make the naming a bit more clear I've renamed the key to transition_status in d05b116, for the advanced query we can use transition_query if that makes sense.