related tasks in status

[Ivan Andrieiev]

Is it possible to count the number of tasks that are related with a task, and which were added when the task was in the "In Progress" status.

[Trudy Claspill · Accepted solution]

Hello @Ivan Andrieiev 

Can you provide more information about your scenario? What problem are you trying to solve? How often do you need to get this information? What do you need to do with the information when you have it?

[Ivan Andrieiev]

@Trudy Claspill  Hi

Hi

our workflow with testing tasks is such that we link bugs to it.
If no bugs are detected during the testing process, the task moves to the "Closed" status, if detected, it returns to the "In progress" status, this happens from the intermediate "Feedback required" status. When returning the task to the "In progress" status, new bugs are linked each time it is changed to this status.

[Trudy Claspill]

What link type is used when you link the bugs to the task?

Is that link type used with any other issue type pairs besides bugs and tasks?

Would bugs and tasks be linked this way at a time when the task is not set to the In Progress status?

Is the bug linked to the task before the transition occurs, or after the transition occurs, or at the same time the transition occurs?

[Ivan Andrieiev]

Hi  

1. We use relates to when we find bugs. 

2. Yes it use with other types issues task and task or maybe epic with epic

3. They will be relate to tasks, but they status will be @ "Closed"

4. Bugs link to tasks in status "In progress", they don't link when task in other status..

I hope I understood correctly.

[Trudy Claspill]

Do you want to get this information for one specific task at a time? Or do you want a report that shows these counts for all tasks that match a query you define?

Do you need to get this report once, or will you need to get the report multiple times?

Is the link between the bug and the task ever deleted, or does it remain forever?

Do you have access to any third party applications that extend the search capabilities for Jira, like JQL Tricks Plugin or Adaptavist Scriptrunner?

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=jql

Do you have access to any third party applications that extend the reporting capabilities of Jira?

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=reporting

Are you open to adding third party applications to your Jira system to get this report, or to make it easier to get this report?

[Ivan Andrieiev]

At the moment, my management wants to get by with the tools provided by Jira without additional plugins. Well, I understand that we will take one task in particular and analyze how many bugs were introduced in it. It would certainly be ideal to do this for a group of tasks, but I can't even logically think of a bug-finding scheme.

[Trudy Claspill]

Issue searching include the linkedIssues function which will retrieve the list of issues linked to a specified issue using a specified type of link:

issue in linkedIssues(<task issue key>,"relates")

If you add to this a criteria that the issue must be bugs, that will give you the list of bugs linked to the task with the "relates" link.

issue in linkedIssues(<task issue key>, "relates") and type = Bug

The search results screen shows the number of issues that match the criteria

Without third party applications any other possible solution using native functionality will be more complex. You could use Automation Rules to track when the link is created, and include steps in the rule to execute the above JQL and save the count of the issues in the results to a custom field in the Task. If you wanted to explore that solution I would strongly advice you to use a custom Link Type that is used only for relating Bugs to Tasks. Using a link type that is used for different pairings of issue types, and using the "relates" link specifically, would make the Automation much more difficult to construct.

[Ivan Andrieiev]

@Trudy Claspill 

I suppose last question, maybe you know smart value witch can count how many tasks was relates?

[Trudy Claspill]

Have you constructed an Automation Rule for this? If so please show us the rule.

The Lookup Issues action can be used to retrieve a list of issues based on a JQL statement. After that action there is a smart value {{lookupIssues}} that contains the results set. It is a list type object. You can use {{lookupIssues.size}} to get the count of items in the list.

[Ivan Andrieiev]

I am thinking about that. I have some ideas, but it just ideas 

[Trudy Claspill]

The rule you have shown is not constructed to retrieve a list of issues and get a count of the issues in the result set.

The rule you have constructed is for an entirely different purpose. If you have a question about creating a rule to satisfy a different purpose, please start a new Question post in this community.

[Ivan Andrieiev]

@Trudy Claspill  thank for now, I will do something