INFRA project issues migration from Jira to Github

27 views
Skip to first unread message

Herve Le Meur

unread,
Jan 12, 2022, 8:50:38 AMJan 12
to Jenkins Developers
Hello!

As some of you might have already noticed, all issues related to the Infrastructure project have been migrated from Jira (https://issues.jenkins.io/projects/INFRA/issues) to Github (https://github.com/jenkins-infra/helpdesk/issues?q=label%3Aimported-jira-issue)

It's almost done, several docs linking to the jira project still have to be updated to point to this Github repository.

You can find more details and the related infra meeting notes here: https://github.com/jenkins-infra/helpdesk/issues/9

Regards,

Hervé

Ullrich Hafner

unread,
Jan 12, 2022, 6:42:53 PMJan 12
to JenkinsCI Developers
It seems that the reporters (and assignees) of the issues have not been mapped. Is this planned? 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e564ed63-3fd7-4888-a8b5-6630974ed91cn%40googlegroups.com.

Tim Jacomb

unread,
Jan 13, 2022, 2:46:25 AMJan 13
to jenkin...@googlegroups.com
The information was included in the import

All of them have the reporter, and the ones assigned have it in the expanded details section, e.g 

GitHub doesn’t let you report as another user, and assignee would require a Jira -> GitHub mapping, which might work for the INFRA project as it’s unlikely to be many people assigned to, but also not very valuable info IMO.

There’s hundreds of old issues to review and likely close which should end up with a much more manageable backlog

Ullrich Hafner

unread,
Jan 13, 2022, 3:50:36 AMJan 13
to JenkinsCI Developers
Am 13.01.2022 um 08:46 schrieb Tim Jacomb <timja...@gmail.com>:

The information was included in the import

All of them have the reporter, and the ones assigned have it in the expanded details section, e.g 

GitHub doesn’t let you report as another user,

I see, this is a real drawback of the import. I am using a „reporter" filter quite often in Jira. 

and assignee would require a Jira -> GitHub mapping, which might work for the INFRA project as it’s unlikely to be many people assigned to, but also not very valuable info IMO.

I think it is a very valuable information who actually fixed a bug. But since the information is at least visible in the description text at least a workaround is available... 


There’s hundreds of old issues to review and likely close which should end up with a much more manageable backlog

On Wed, 12 Jan 2022 at 23:42, Ullrich Hafner <ullrich...@gmail.com> wrote:
It seems that the reporters (and assignees) of the issues have not been mapped. Is this planned? 


Am 12.01.2022 um 14:50 schrieb 'Herve Le Meur' via Jenkins Developers <jenkin...@googlegroups.com>:

Hello!

As some of you might have already noticed, all issues related to the Infrastructure project have been migrated from Jira (https://issues.jenkins.io/projects/INFRA/issues) to Github (https://github.com/jenkins-infra/helpdesk/issues?q=label%3Aimported-jira-issue)

It's almost done, several docs linking to the jira project still have to be updated to point to this Github repository.

You can find more details and the related infra meeting notes here: https://github.com/jenkins-infra/helpdesk/issues/9

Regards,

Hervé

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e564ed63-3fd7-4888-a8b5-6630974ed91cn%40googlegroups.com.


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/DB75232C-4F54-4BC7-AD27-94F2D5292C87%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

Herve Le Meur

unread,
Jan 13, 2022, 4:45:26 AMJan 13
to jenkin...@googlegroups.com
On Thu, Jan 13, 2022 at 9:50 AM Ullrich Hafner <ullrich...@gmail.com> wrote:

Am 13.01.2022 um 08:46 schrieb Tim Jacomb <timja...@gmail.com>:

The information was included in the import

All of them have the reporter, and the ones assigned have it in the expanded details section, e.g 

GitHub doesn’t let you report as another user,

I see, this is a real drawback of the import. I am using a „reporter" filter quite often in Jira.

and assignee would require a Jira -> GitHub mapping, which might work for the INFRA project as it’s unlikely to be many people assigned to, but also not very valuable info IMO.

I think it is a very valuable information who actually fixed a bug. But since the information is at least visible in the description text at least a workaround is available...

As you noticed, there is additional information in the issues body in a <details> block, closed by default to avoid clutter.

Tim already said what I was about to respond about the author and assignee possibilities or lack of.

My regret is the fact I've learned about the "notifyUsers=false" Jira REST API parameter too late.

Ullrich Hafner

unread,
Jan 13, 2022, 5:41:13 AMJan 13
to JenkinsCI Developers
>
> My regret is the fact I've learned about the "notifyUsers=false" Jira REST API parameter too late.
>

Well, I think it is very important to notify reporters that their issues have been moved to a new system.

Daniel Beck

unread,
Jan 13, 2022, 2:21:57 PMJan 13
to jenkin...@googlegroups.com
On Thu, Jan 13, 2022 at 11:41 AM Ullrich Hafner <ullrich...@gmail.com> wrote:
Well, I think it is very important to notify reporters that their issues have been moved to a new system.

Once, sure, but 500+ times? 🙃
Reply all
Reply to author
Forward
0 new messages