Field Availability for Mapping

[Darrell Hobson]

We are attempting to use an AddOn (LeanIX) that will enable us to synch Jira Epics with factsheets in LeanIX.  

In the field mapping configuration page, only a handfull of fields (name and summary) are available in Jira to be mapped to an epic in LeanIX.  How do you expose additional mapping fields in Jira?

[Dave Rosenlund _Trundl_]

Hi, @Darrell Hobson. Welcome to the community  👋

I moved your post to 'App Central' — the place in the community for questions related to Atlassian Marketplace products.  I also added a "leanix" tag to your post to increase the likelihood of your question being seen by a user or the app maker.

That said, LeanIX for Jira is a new product with relatively few installs so far.  There's nothing wrong with that; I only mention it because it means there will be relatively few (if any) fellow users here on the community to help you.

This is a case where you will likely get help faster by contacting the LeanIX support team directly.

Best,

-dave

[Darrell Hobson]

Hi @Dave Rosenlund _Trundl_ ,

Thanks for your response.  I guess that my question could be more generic.  In other words, how do you add fields for mapping regardless of the application to which you are syncing?  

[Dave Rosenlund _Trundl_]

Forgive me, but I may not understand the question. I.e., I am having trouble imagining a generic answer.

At a high level, most fields in a Jira record can be accessed (securely) via the Atlassian APIs. Presumably, LeanIX can/will do that for you based on fields they believe to need to map to their product.

So unless we understand your Jira < > LeanIX integration goals in more detail, I'm not sure how to answer your question.

In particular, say more about what you mean exactly when you say 'fields for mapping.'

In my head, I am imagining you want to map Jira Field X >>to>> LeanIX Field Y -- but I may be getting it all wrong  🫤

P.S.  I know nothing about LeanIX so that is part of the problem, and why I think you need to talk to them.

[Darrell Hobson]

Hi David,

Understood.  And I appreciate your assistance and need for clarification.  I engaged LeanIX support previously, and they suggested that I reach out to Jira support or community forums.  I am attempting to map fields from a Jira epic to a LeanIX epic factsheet (a record) for a one-way (Jira to LeanIX) sync process facilitated by the LeanIX AddOn. When an epic is created in Jira an Epic factsheet (a record) will be created in LeanIX.  Subsequently, when that epic is updated in Jira, the mapped fields on the associated LeanIX factsheet will be updated.  

I want to be able to map the following Jira epic fields to the LeanIX fields:

Jira Epic Fields:

• ID
• Name
• Description
• Comments
• Start Date
• Due Date

LeanIX Fields:

• ID
• Name
• Description
• Comments
• Start Date
• End Date

The field mapping page is what you would expect:

LeanIX Epic Field                    Direction                 Jira Epic Field

Dropdown List                         Jira -> LeanIX        Dropdown List

The LeanIX dropdown list contains all of the fields above, but the Jira dropdown list only has Name and Summary available for mapping.

So when I suggested a "generic" functionality, I meant that I think Jira syncing with other external applications would be a common practice, and that would lead me to believe that certain fields are exposed out of the box for mapping purposes.  

I hope that this clears things up some.

[Dave Rosenlund _Trundl_]

It certainly does, @Darrell Hobson. Thank you!

Unfortunately, though, this brings us back to where we started. You'll have to contact LeanIX support on this.

Jira doesn't have a field mapping feature. The Atlassian Marketplace partners who develop the add-on applications use the Jira APIs to create the 'mapping' you describe. 

I.e., that dialogue box is something LeanIX developed.

Like you, I would just expect it to work without any further action required on your part (since those are just std. Jira fields). You'll have to ask them what might be causing this problem. It may require some sort of administrative change on the Jira side of things, but they should be able to guide you to that needed change.

As a precursor, you could ask your site administrator if there is a permission scheme your company is using that might be the cause. But my guess is they're going to suggest the same thing I am, 'talk to LeanIX'  🙂

Good luck! And please do let us know how things get resolved.

-dave