20. Issue List post migration

1

Closed Issue are showing as Open In Jira

Identified BY SIFT 06/23/2929

JI-32

https://sift.atlassian.net/browse/CON-3377
https://github.com/SiftScience/code/issues/20472

There is a condition which I have put to check for the label and if not found then we take default value of state as “Open“. This could only be present in one project, “Content Abuse“ because this is the default project if there are no project label specified in github.

Move non labelled issues to newly created projects - “Migration Audit“ @Travis Alexander - Move to ENG project NOT Migration Audit

Fixed In Code

@Travis Alexander Jun 24, 2020 - This was an oversight in the migration code and can be resolved without a re-migration by synchronizing a CSV file (GitHub and Jira) that will update existing issues.

Issues that do not have any labels will need to be reviewed by the customer.

1 A

Non-labeled issues are in the Content Abuse project and not necessarily part of Content Abuse

Identified by Empyra 06/24/2020

JI-33

@Travis Alexander - Move to ENG project NOT Migration Audit

done CONFIG

@Travis Alexander Jun 24, 2020 - All non-labeled issues will be moved to the new Engineering(ENG) project. The status of these issues may be updated by the resolution of #1 if appropriate.

2

Epics in the team backlog are listed as unlabeled Identified BY SIFT 06/23/2929

JI-34

Require more information

Epic summary should also be copied to Epic name

POST MIGRATION WORK

@Travis Alexander Jun 24, 2020 -This can be resolved in-app without a re-migration by re-uploading a CSV and copying the Summary to the Epic Name field.

3

Formatting is all broken

Identified BY SIFT 06/23/2929

JI-35

https://github.com/SiftScience/code/issues/34174 vs. https://sift.atlassian.net/browse/ENG-2

It is very difficult in the code to identify these formats. Usually api sends any formatting information enclosed in ticks “`“ but doesn’t give any idea about what kind of formatting it has, Whether its a table or a code block, just a list or a formatted text. So it becomes very difficult to identify the formatting formation.

Reply to a comment is not supported in Jira.

WONT DO

@Travis Alexander Jun 24, 2020 - As verbally noted, we are unable to retain formatting because at runtime, there is no way to identify the different formatting commands and resolve them when inputted into Jira. This was noted to Amina early on.

4

Descriptions in github appear as comments in JIRA

Identified BY SIFT 06/23/2929

JI-36

I think this is a bug in the utility where it takes description as first comment from github to jira

FIxed in code

@Travis Alexander Jun 24, 2020 - “Descriptions” in GitHub are technically stored as a comment by the user. We can optionally copy this to the Description field in Jira if necessary. It will have a duplicate as the first comment. This can be entirely resolved if a re-migration was performed.

5

There are no checkboxes!!! We use checkboxes a lot to track how we are doing on an issue with multiple steps to resolve

Identified BY SIFT 06/23/2929

JI-37

https://github.com/SiftScience/code/issues/43068  

Jira doesn’t support checkboxes in the comments or body of the issue

Wont do

@Travis Alexander Jun 24, 2020 - If a re-migration was performed, we can potentially look at dumping this into the description field, but this would need investigated.

6

For existing epics in github/zenhub, we lost the connection between the epic and the subtasks

Lost Zenhub Pipelines

Identified BY SIFT 06/23/2929

JI-43 JI-44

https://github.com/SiftScience/code/issues/41195

Require more information

Fixed In Code Pipelines Not possible

@Travis Alexander Jun 24, 2020 - This was specifically looked into prior the the migration and we were unable to determine how these links we made or where they exist. A specific resolution is not yet defined as we need a specific example.

@Travis Alexander Jul 9, 2020 -

7

We lost the connection to the PRs that had the change and when they were merged

Identified BY SIFT 06/23/2929

JI-38

. https://github.com/SiftScience/code/issues/35398 https://sift.atlassian.net/browse/CI-71

Jira identifies the commit and PR information using smart commit message and naming conventions - https://support.atlassian.com/jira-software-cloud/docs/integrate-your-issues-and-development-tools/

After connecting their Github to Jira users still have to use smart commit syntax in branch names and commit comments before they can see their PR information from Github to Jira. Unfortunately this is highly unlikely that users would change their existing branch names jits so that they appear in Jira development panel.

Wont do

@Travis Alexander - Linking to the actual historical commit is not possible because the commit itself does not contain the Jira issue key. The best we can do is retain the ID of the GitHub issue. All future commits will be displayed assuming the commit is associated with the Jira key.

8

CP Project is empty

Identified BY SIFT 06/23/2929

JI-39

@Travis Alexander - There should definitely be more issues within the CP project and are labeled as such within GItHub.

Label = “a_ConsolePlatform” is missing from Mapping document and should be mapped to “CP” project

https://github.com/issues?q=is%3Aopen+is%3Aissue+label%3Aa_ConsolePlatform+

One issue was migrated and is closed. Need to confirm with customer.

done

@Travis Alexander Jun 24, 2020 - A single issue was in fact migrated for this project (per the labels). The issue has a resolution and is therefore not displayed on the backlog. Will need to be confirmed by the customer.

9

URL Link not functioning

Identified BY SIFT 06/23/2929

JI-40

This is the API URL and should be hidden

FIXED IN code

@Travis Alexander Jun 24, 2020 - We will likely want to hide this URL from the Jira issue as it simply displays the API url and is not helpful to the user. Perhaps we can look into supplying a better, more useful link if necessary but was not necessarily part of the migration scope.

@Gaurav (Unlicensed) Jul 10, 2020 - We will give a link to the issue in the UI so that they can directly go to the issue in github

10

Closed issues do not have a resolution

Identified by Empyra 06/24/2020

JI-41

Issues migrated as closed should also have a resolution of ‘Done’ so they are properly displayed throughout Jira.

POST Migration activity

@Travis Alexander Jun 24, 2020 - Issues can be fixed to contain a resolution by using ScriptRunner or a CSV upload. This is an easy fix and not immediately impacting users but needs resolved. It can also be done using bulk operation.

11

User mapping changes

JI-42

May want to re-assign any non-mapped users to a different account

Need to add a new engineering manager that will be added to mapping document.

NAME: Phani Srikar Ganti HANDLE: 
phanther

Add New User to mapping document

CHange required

Github handle - phanther

User is present in Jira so we can get the Atlassian ID

12

Closed Epic Show up in Backlog View

JI-57 JI-55 JI-48

All closed Epics are showing up in the sprint backlog

There is a field called as epic status. Which should also be marked as closed to stop epics from appearing in Sprint backlog.

post migrationactivity

Use the bulk change operation to change value of epic status to closed for all epics which have status as closed

13

Placeholder accounts and Values Required

JI-56 JI-46

Default Creator asaify@siftscience.com
Default Reporter asaify@siftscience.com
Default Issue Assignee UNASSIGNED
Default Comment Creator asaify@siftscience.com
Default Project Engineering (ENG)

We need values for all these

fixed in code

After getting the values set them in code

@Travis Alexander Jul 9, 2020 - See values in column to the left.

14

Screenshot shows as <img> tag in comments

JI-47

images are appearing with IMG html tag in comments

This is very difficult to achieve as there is no set patterns for such images and if i try to search them in the body and replace them then I may end up replacing the one which is not a attachment.

wont do

15

Formatting for code block not correctly migrated

JI-45

Code block missing formatting info

This is very difficult to achieve as there is no formatting information passed from GH

wont do