Open lukaszachy opened 6 months ago
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)'.
@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 https://github.com/psss/did/issues/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.
List of interesting statuses sounds nice, it would give even a bit more flexibility to the user.
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.
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
Seems that states and workflows can be too different