Mapping field values from SalesForce to JIRA

  • 1
  • Question
  • Updated 2 years ago
  • (Edited)
We have mapped the SalesForce Component field to the JIRA Component field. For most of the projects, the values between the two systems are the same. One project would like to modify the value of Component on the creation of the JIRA ticket. If I modify the "mapped values" of the component field for this project, the JIRA tickets come across with the new "mapped" values, but all other projects no longer pass the Component field (the value in the JIRA ticket is empty). Is it not possible to map SOME values in a field, but not ALL values? This project has over 200 Components and I just need to change the value of 2 of them.
We do have a plan to change the value of these Components on the SF side (and then no values will need to be mapped), but in the mean-time, we would like to map these two values in JIRA.

Example:

SF Value                        JIRA Value          Mapped Value
Assignments                  Assignments
Grade Book                   Grade Book         Assignments
Registration                   Registration
Class                             Class                    Assignments         

I know its a bit convoluted, but until we can get SF updated, I need to make sure all SF cases with a Component of Grade Book or Class are created in JIRA with a Component of Assignments. Can I do this without having to map the values for all 200 Components currently in the JIRA project. I the example above, if I remove the Grade Book and Class components, then add the mapping to Assignments, will that work? Will the remaining Components still be set in JIRA?
Photo of Jeanne Howe

Jeanne Howe

  • 33 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Adrien Low

Adrien Low, Alum

  • 85 Posts
  • 3 Reply Likes
Hello Jeanne,

Can you please provide us with the following information to investigate this further?
  • Your JIRA and Connector version
  • The field type of the SF field mapped to the JIRA Component/s field
  • JIRA -> Left panel under Cloud Connectors, click Mappings -> Your Mapping -> Configure -> Full screenshot of all your field mappings
  • JIRA -> Left panel under Cloud Connectors, click Mappings -> Your Mapping -> Configure -> Locate the field mappings for both Inbound and Outbound -> Map Values -> Full screenshots
  • Steps you took to re-create the behavior with screenshots, if possible

Regards,
Adrien
(Edited)
Photo of Jeanne Howe

Jeanne Howe

  • 33 Posts
  • 0 Reply Likes
Adrien,
Here is the info you requested.

Connector 6.0.15
JIRA 7.2.4
SalesForce field - JIRA Initial Assignee (picklist)
JIRA field - JIRA System Component/s field
Field Mapping for the field - screen shot attached. Currently no values are mapped
In/outbound mappings - screen shot attached

Current process:

Create a SF case and select a JIRA Initial Assignee
Create a JIRA ticket from the SF case
    On mapping, the JIRA Initial Assignee is mapped to the JIRA Components field
        (see screen shot - JIRA Map Values)
    No field values are mapped
    The JIRA Component is set to the value of the SF JIRA Initial Assignee field
    Within JIRA, the JIRA Component Lead is set to a valid JIRA user
        (see screen shot - JIRA Component Lead)
    JIRA ticket is assigned to the JIRA Component Lead

What we would like to do:

 Create a SF case and select a JIRA Initial Assignee
 Create a JIRA ticket from the SF case
    On mapping, the JIRA Initial Assignee is mapped to the JIRA Components field
          If the JIRA Initial Assignee = nikolay_nikolov
             Map the field value of JIRA Initial Assignee -> Components to be LST_CXG
                  (see screen shot - JIRA Map Values Nicolay)
             Within JIRA, no Component Lead is set for this Component
            JIRA ticket is unassigned but a search on Component = LST_CXG can be executed.
         
         If the JIRA Initial Assignee != nikolay_nikolov
           JIRA Initial Assignee is mapped to the JIRA Components field (see screen shot)
           Field values are mapped for nikolay_nikolov only, mapping for remaining values are empty                        (see screen shot - JIRA Map Values Nicolay)
          The JIRA Component is set to the value of the SF JIRA Initial Assignee field
           Within JIRA, the JIRA Component Lead is set to a valid JIRA user
                 (see screen shot - JIRA Component Lead)
          JIRA ticket is assigned to the JIRA Component Lead


I hope this explains it.

Photo of Jeanne Howe

Jeanne Howe

  • 33 Posts
  • 0 Reply Likes
More screen shots

Photo of Kevin Lew

Kevin Lew, Official Rep

  • 50 Posts
  • 2 Reply Likes
Hello Jeanne,

Thank you for the provided information. 

We are able to replicate this issue and we have raised this to our Development team for further review. We will get back to you once we have any updates from them.

Regards,
Kevin