Referencing Jira Projects using an Insight Custom Field

[Michael Gaskin]

I want to create an Insight Custom Field that allows the user to indicate which Jira Projects are affected by an issue. By default, Insight already knows about all of our Jira projects - they're available under the Project attribute type. But in order to use them in an Insight Custom Field, they would have to be created as objects in their own right. 

Since Insight is already being fed a list of our Jira projects from somewhere, is there an easy way to turn them into standalone objects that can be selected in an Insight Custom Field?

[Nader Nassif]

Hi Michael,

You can use Filter objects with attributes option to show the attribute value on the custom field. Also, You can use the option object attributes on issue view on the custom field to show the project attribute value on the Jira issue. 

You will still see the object name on the jira issue, but the project will be referenced to that object on the issue and on the field. 

Cheers!

Nader

[Michael Gaskin]

Hi Nader, 

That is indeed possible, but it presupposes that I already have objects containing the Jira Project attribute, which I do not. Consider this example:

Let's say I have an object type called Application. Each Application object has a Jira Project attribute called Project. It would be easy to create a custom field that looks up Applications and displays their associated Projects, as you described. 

But what if I want to refer to Jira Projects directly? The custom field would be "Affected Projects:" and you would choose the Insight objects representing the projects affected by that issue. 

Here's one way I found that might work: Use the Jira REST API to return a list of all projects in JSON format, and set that up as an Insight import configuration. Going to "[yourcompany's jira domain] /rest/api/2/project" will return such a JSON.

[Nader Nassif]

Hi Michael,

Insight custom fields currently are designed to return objects. Thus, in your particular case it works differently.

You can add a feature request for my developers at jira.riada.io so we can add more custom field types that can return attribute values in the future. 

We have a handful of REST calls that you can choose to work with as well. One interesting in this case would be this one, you can develop a script that returns only if the field type is of int value 6 (returns a Project attribute). You can combine that script with your REST call to setup a powerful script that shows which project is connected to which object.

Cheers!

Nader