incubator-devlake icon indicating copy to clipboard operation
incubator-devlake copied to clipboard

Published 20 hours ago • verified publisher icon apache

[Feature][Jira] Transformation based on JQL

Open tim-goto opened this issue 2 years ago • 14 comments

Search before asking

  • [X] I had searched in the issues and found no similar feature requirement.

Use case

Instead of transformations based on the differnet issue types, we would like to enter JQL queries to select the appropriate tickets since that gives a little more flexibility

Description

No response

Related issues

No response

Are you willing to submit a PR?

  • [ ] Yes I am willing to submit a PR!

Code of Conduct

tim-goto avatar Jun 06 '23 06:06 tim-goto

Thanks for the suggestion. Can you provide a more concrete example?

klesh avatar Jun 07 '23 07:06 klesh

Sure: We have a board where multiple components of a single product are tracked, each component has different deployments, code bases and so on.. We would like to track DORA metrics for each component of the product but there is currently no way to distinguish tickets on a board in devlake. For the moment we created individual JIRA boards filtering for the components but it would be nice to have a more granular selection in the devlake transformations.

tim-goto avatar Jun 07 '23 07:06 tim-goto

Not sure if I understand you correctly, sounds like you would like the Jira Scope to be like Board + JQL instead of Board alone, so you can group issues from the same Board into different DORA projects?

klesh avatar Jun 08 '23 07:06 klesh

Yes, either that or Jira ticket selection to be JQL + issue type instead of just issue type

tim-goto avatar Jun 08 '23 07:06 tim-goto

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar Jul 09 '23 00:07 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar Aug 11 '23 00:08 github-actions[bot]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

github-actions[bot] avatar Aug 18 '23 00:08 github-actions[bot]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

github-actions[bot] avatar Aug 26 '23 00:08 github-actions[bot]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar Oct 29 '23 00:10 github-actions[bot]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar Dec 29 '23 00:12 github-actions[bot]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

github-actions[bot] avatar Jan 05 '24 00:01 github-actions[bot]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar Mar 06 '24 00:03 github-actions[bot]

Still important to me

tim-goto avatar Mar 08 '24 07:03 tim-goto

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar May 10 '24 00:05 github-actions[bot]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

github-actions[bot] avatar May 17 '24 00:05 github-actions[bot]