Component: Assign to Jira based on Defect description and comments

Question

Hi there,

I am looking for Jira capability to learn from historical defects data and update the component based on code fixes which happened in the past for similar issues etc.

I saw that you are showing duplicate defects but i need a component suggestion and I should be able to limit the data timelines for this recommendation.

All this I want after raising the defect and not before the defect creation. Any solution already available please let me know.

Thanks for your support.

Regards

Archana

Bill Sheboy · Answer

I am not aware of any built-in features for that type of analysis for customers data which is available to us.  Perhaps check the Atlassian Marketplace for addon apps.

Archana Agarwal_8j1371 · Answer

Hi Bill,

Thanks for your response.  #1 , It is not as simple as I can say assign a component based on some fields etc.
Does Jira has any ML or intelligence or defect prediction based on historical data which can say that similar issue is caused before and xyz component was fixed etc.

I would like Jira to tell me where could be the issue , in which area in a complex Microservice architecture.

Bill Sheboy · Answer

Hi @Archana Agarwal

What are you asking to do?  For example do you mean:

* based on information saved with a Jira issue, update the Component value(s)
* based on the code changes made and stored in source control outside of Jira, update a Jira issue to change the Component value(s)
* something else?

You can do #1 with the built-in automation for Jira or bulk edit features...provided you can consistently determine what fields/data to check and what Component value(s) to set.

I am not aware of any built-in features to perform #2, as that would require arbitrarily querying the source control store for information about 1-to-many files.  Theoretically, if you had a well defined list of source files and criteria to check, an automation rule could call the REST API for your source control tool to gather information and update Jira issue Component values.

Kind regards,
Bill