Mapping process for issue types

General Questions
, , ,
1

Originally asked by Joanna Kwiatek Tokarz on 02 November 2020 (original question)

Hi,

Can you please inform us how to do the mapping process for issue types for JIRA and Azure DevOps side?

Suppose we have one issue “task” which has three states like open, resolved, and closed.

so, we need one to many mapping processes:

task --> open,
task --> resolved
task --> closed

I am adding states mapping.xlsx (old community)a detailed mapping. In a column, B is the status that comes from JIRA, and in a column, C is the status that we want to have in ADO. The issue is, that somehow we need to distinguish states within different types of issues. In practice, we need to have a mapping for tasks, mapping for the user stories, and mapping for the bug. How should we extend the script?

2

Answer by Francis Martens (Exalate) on 04 November 2020

In the incoming sync on your ado side you can have multiple maps, one for each issue type.

Something like

incoming ADO - untested

def statusMappingTask = [
    "Open" : "To do",
    "In Progress":"In Progress",
    "Done" : "Closed",
]

def statusMappingStory = [
    "Open" : "Triage",
    "In Progress":"Doing",
    "Done" : "Done",
]


def targetStatus = "Open"
if (issue.type.name == "Task") {  targetStatus = statusMappingTask[replica.status.name] ?: "Open"}

if (issue.type.name == "Story") {

  targetStatus = statusMappingStory[replica.status.name] ?: "Open"

}

Comments:

Joanna Kwiatek Tokarz commented on 12 November 2020

Hi,

We have an error:

incoming sync: first sync error
Script error details: Cannot get property ‘name’ on null object. Error line: Script20.groovy:154
Sync for connection 1QJiraPAS_to_PGDevOpsAS is blocked
Nov 12, 2020 14:28:41

Francis Martens (Exalate) commented on 13 November 2020

When syncing for the first time, issue.type is not set (as the issue doesn’t exist yet)

You will have to construct the processor to take that into account.