Reportportal: Use information regarding Jira status in AutoAnalysis

[priyankachaturvedi30]

Currently, we have a system which performs AA on the following base -

1. All Launches 2. Launches with same name 3. Only Current Launch
   But what if I want to perform AA on a specific launch base. How can we achieve it?

Suppose, I have a daily run being executed and there is a product bug in the system which I categorized.
Launch 1 - PB_123
It got AA in next 3 runs and got fixed in 4th run. So, for Launch 4 - that issue got fixed and I close the jira.
Now, say after 2 runs in Launch 6 - the issue again comes. This time the issue again got AA since it was baseline previously. Adhering to the above use-case, since the issue got AA - I might miss that the issue is reopened again (because its a new issue for me now but it got AA). The solution to this problem can be providing an option to perform AA on the previous run and not across all runs. Suggest you to provide one option for selecting base like - Last Launch with same name (or a Custom Launch name to be picked by user).

[evjlobanova]

@priyankachaturvedi30 in version 5.3 we have added a possibility to use in AA the latest results of execution. So that if you change for execution defect type and link to BTS, in the future runs we will use only latest results. So partly it is resolved.

But I suppose that real problem is that now ReportPortal can not use information about Jira ticket status in the auto analysis. And user can not filter the test case by Jira ticket status.

We are planning to improve integration with Jira.
And for instance you can auto analyze your launch. You filter AA items in the launch and find that several from them are linked to closed Jira ticket. You reopen or create new bug in Jira.
Then you run the test one more time, auto analyze them, and AA link failure to the new bug in Jira.

[priyankachaturvedi30]

Thanks @evjlobanova . This can definitely be one of the solutions. But in such a case as well, I would need to go and re-visit all my auto-analyzed issue. I think of one more way to achieve it - Can we not make use of the timeline information and derive the issue status from it?

Consider the above screenshot - there was the same issue that has recurrent occurrence in build 15, 19, 20, and 24. As you can see from the timeline - it got fixed in some builds and again failed in some builds. For such an issue - since it would be AA each time, it would be difficult for me track down it each time via JIRA. In fact, it would be very helpful for me if I can find such information derived through timeline via some widget or flag at launch level itself. Please let me know your thoughts on the same.

[evjlobanova]

@priyankachaturvedi30 This idea is close to my, because it is also connected with Jira integration refactoring. Because now we can not show this information.

So in scope of refactoring, we will discuss your use case.