Automation for linking two issues with a common (text) field

[Richard Canlas]

Example: 

Issue type "A" has a field to input the "Company Name" in text.

When issue type "B" is created and the text in the field "Company Name" is the same as in Issue type "A", I want to be able to automate the linking of both issues based off the same text in "Company Name" when Issue type "B" is created.

Please help.

Thanks.

[Aron Gombas _Midori_]

If I understand correctly, you want to associate each issue with a company (through the "Company Name" field) and you want to link the issues that are associated with the same company. If so, then the solution you're thinking about may not be the most intuitive.

Problems that I see:

1. For example, if you have 20 issues associated with "Acme Inc.", then each of those issues will have 19 issue links? Will that be easy to navigate?
2. If someone enters the same company as "Acme" while someone else as "Acme Inc.", then the link will not created. You need more validation here...

Alternatives:

1. Why don't you model your companies as Insight object? Then link issues to these Insight objects?
2. Or model companies as a special issue type? Then link the actual issues through an issue picker custom field?
3. Or model companies as "components"?
4. ...

[Richard Canlas]

@Aron Gombas _Midori_ 

Problem #1 answer: 20 issues will never be associated with the company. 

The hierarchy I'm working with is:

Client (Standard Issue Type) > Product Name (Epic) > Project Stage (Task) > Tasks (Sub-tasks)

For each client, there are at most 5 products at a time. 

The product is what I want to associate with the client. 

Problem #2 answer: I believe if we spot these typos during our weekly meeting, they will be fixed. 

Alternatives:

1. What is an insight object?

2. Can you elaborate on this please

3. Please elaborate too

[Aron Gombas _Midori_]

Answers (although you could find these with 2 min of Googling, to be honest):

1. Insight was an asset management app that has been acquired by Atlassian and became a part of JSM. You can model every sort of entities as Insight objects and link those to Jira issues. In your use case, you could model your customers as Insight objects. (I know many teams are using Jira as a sort of CRM solution like this.)
2. You could define a custom issue type "Company". Then create one issue for each of your customers. Then create an issue picker type custom field and configure it to enable choosing one issue of the "Company" issue type.  Then you can add this field to your concrete issues and voila!
3. Basically the same idea, but you model your customer as components. Component is a built-in entity in Jira that serves Software Management use case, but it could be useful here as well.