Suggest an Idea

[mariusbirk]

Hello all,

in the WebConnector for JIRA it is possible to get the connection type via the "IssueAsRawXML" query, but not with the "issues" query. It's necessary for many users to get this important field and the "issues" query is here the best query to work with JIRA.

[chrisbrain]

Hi - Can you just clarify by what you mean by 'connection type'?

An example of how this looks in the XML version of the response would also be useful.

[mariusbirk]

In JIRA it is possible to connect issues with each other. Therefore different connection types could be used. For example: issue1 "relates to" issue 2 or issue3 "blocks" issue4. In the data from the webconnector its possible to see which issues are linked with each other (issue1 and issue2) but the connection type (relates to) is missing. 

In screenshot you see that via the webconnector with query "IssueAsRawXML" it is possible to get the "name", but with query "issues" it is not possible..  

[chrisbrain]

Thanks - I think the reason these aren't included in the current issue is there is only a single row per issue and there could be multiple links.

Do you have an idea how you would represent all of these links in a single (or multiple) columns for a single issue?

[chrisbrain]

The alternative would be to add some sort of LinksForIssue table which takes an issue ID.

[Steffi]

Hello @chrisbrain ,

I would suggest a separate table that could look like this:

The statement that there is only one line per issue is not 100% correct.
I also assumed this 😉 but I know the following case.
Create a custom field of the type checkbox with multiple selections.
If several options are clicked, several data records will be created for the issue with the same ID!

[chrisbrain]

@Steffi Thanks for this.

We could add a LinksForIssue table - my only concern is that you would then have to construct a for/next loop to run this for potentially 1000s of issues which could be slow and it's to get data which was already present in the API responses used to build the Issues table.

Would it be useful to add an 'InwardIssues' column to the existing issues table which for example concatenated together the links using a format something like:

issue1Id|issue1key|issue1LinkType,issue2Id|issue2key|issue2LinkType,issue3Id|issue3key|issue3LinkType

And similarly for 'OutwardIssues' and then these could be parsed out into related tables in the load script?

[mariusbirk]

@chrisbrain 

this sounds great! It would be very useful for us to have two columns (InwardIssues & OutwardIssues) as you described. What would be the further process for this feature request?

Regards,

Marius 

[chrisbrain]

Hi,

Thanks - nothing else you need to do your side for now 🙂

[mariusbirk]

Hi, this means that potentially with the next WebConnector Version this is possible? 😉

[chrisbrain]

@mariusbirk Yes possibly - I am actually looking at it today.

I realised the Issues table does already have fields_issuelinks_ids and fields_issuelinks_keys columns which concatenate these values together.

I guess this is not sufficient - Is it both the inward/outward and linkType you are missing?