wakaleo
commented
2 years ago This is a nice idea; I tried it once and found the JIRA APIs to be prohibitively slow.
Open therevelator opened 2 years ago
wakaleo
commented
2 years ago This is a nice idea; I tried it once and found the JIRA APIs to be prohibitively slow.
therevelator
commented
2 years ago Hi, thanks for the reply,
They’re not slow if the JQL is properly formatted and plus, you can have the feature turned off in the properties
Worth looking into, and many people from work said this would be a great idea
Regards, Ionut
On Sat 19 Feb 2022 at 16:26, John Ferguson Smart @.***> wrote:
This is a nice idea; I tried it once and found the JIRA APIs to be prohibitively slow.
— Reply to this email directly, view it on GitHub https://github.com/serenity-bdd/serenity-jira/issues/119#issuecomment-1046028841, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI3QYUYJ26SOMOYUZPMENLU36SATANCNFSM5OUDA5ZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
--
Ionut Apostu
Mobile: +353 85 815 3486 <+353%2085%20815%203486>
wakaleo
commented
2 years ago The problem is not the JQL queries, it is that you need to do a LOT of queries, because you can't retrieve the requirements structure from the JIRA API in one go - you need to traverse the requirments tree structure, and factor in all the different ways large organisations organize their JIRA repositories.
Would your company be willing to sponsor this work?
therevelator
commented
2 years ago Hi John,
I will surely convey the message to my supperiors and let you know!
Thanks, Ionut
On Sun 20 Feb 2022 at 11:21, John Ferguson Smart @.***> wrote:
The problem is not the JQL queries, it is that you need to do a LOT of queries, because you can't retrieve the requirements structure from the JIRA API in one go - you need to traverse the requirments tree structure, and factor in all the different ways large organisations organize their JIRA repositories.
Would your company be willing to sponsor this work?
— Reply to this email directly, view it on GitHub https://github.com/serenity-bdd/serenity-jira/issues/119#issuecomment-1046196497, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI3QYWKROOWHONTW24CYC3U4CXA3ANCNFSM5OUDA5ZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
--
Ionut Apostu
Mobile: +353 85 815 3486 <+353%2085%20815%203486>
My idea is: if you're indexing all the stories / issues in a project, it would be useful to have (somewhere in the Serenity report) a section which shows the test coverage. How many done stories do we have versus how many done stories are covered by tests (manual, automated, etc).