feat(jira): Allow extra JQL when querying JIRA board#8972
Conversation
| // Look up the DevLake project this board belongs to via project_mapping. | ||
| // This is best-effort: if the board is not yet mapped (e.g. first run or | ||
| // manual trigger outside a blueprint) we leave DevLakeProjectName empty. | ||
| if scope != nil { |
There was a problem hiding this comment.
I see why you did it – the projectName is not available for the data source plugin.
However, the solution seems too hacky and ad hoc.
We need a better solution:
- adding the
projectNameto theDataSourcePluginBlueprintV200interface - adding a new user-definable column to
Boardand using it instead of theprojectNamevariable.
There was a problem hiding this comment.
Can you expand on point 2, how do you see it working? Also is something similar seen elsewhere in the repo?
As what I'm trying to achieve is that the ExtraJql query has the Devlake project name as a template that can be used in the query.
Ideally I don't want to have to manually key project names as we have 1000s of projects and it seems wasteful when the Jira task and blueprint are already running under a project. So auto discovery of the project name to be used in the JQL is my angle.
There was a problem hiding this comment.
I have updated the code to give only the ExtraJQL functionality, removing the templating of DevLakeProjectName to make the PR cleaner.
We can discuss options how/if it's possible to get the Dev Lake Project Name under a separate piece of work.
As ExtraJQL is a beneficial standalone feature and can still work for my needs, I will just have one data scope per project.
2 participants
pr-type/bug-fix,pr-type/feature-development, etc.Summary
When querying the JIRA board for issues, you can apply an optional JQL query to further filter the board, useful when a board has many components on it.
Screenshots