Re: GitHub issues - switching technical tasks

reviewing: Jira issue with link to GitHub PR #1 https://issues.apache.org/jira/browse/MMETRIC-1 translated into GH Issue #12 with same link to GH PR #1 https://github.com/support-and-care/jira-to-gh-issue-dummy-repo/issues/12 and PR # 1 now has a comment linking back directly to GH Issue #12, wit

Re: GitHub issues - switching technical tasks

I implemented linking the Pull Request with the related issues. The GitHub REST API is limited, so I have to add a comment to the pull request with a link to the issue to solve this challenge. I used the MMETRIC jira project for testing, as mentioned in a previous mail. You can see the resu

Re: GitHub issues - switching technical tasks

To avoid lots of spam mails during testing, I think, I should test it with a dummy Jira project. this will also impact in the future any test for data migration, that will have to avoid creating the testing noise: dummy Jira project can be useful for "unit test" of this feature, but we'll need

Re: GitHub issues - switching technical tasks

Le mardi 14 janvier 2025, 14:29:29 CET Sandra Parsick a écrit : > > I'm fine with that. I have to think about the testing because I cannot use > > the original Jira project because a test run would trigger new events in > > the original PR. This would be a waste. > > Coming back to the PR referen

Re: GitHub issues - switching technical tasks

next-release* -> ? (I have no idea) can stay as is - probably will be one next milestone waiting-for-feedback -> waiting for-feedback (new label) new label - I will add backlog -> delete this milestone and no mapping drop - no mapping more-investigation -> more-investigation (new label)

Re: GitHub issues - switching technical tasks

On Tue, 14 Jan 2025 at 09:52, Sandra Parsick wrote: > > > > > I would like to move it to labels. > > We can use a stale action to close inactive issues, pr. > > I found the following milestone in MCLEAN, MJLINK, ARCHETYPE with label > characteristics (and I give the suggestion, if it was possible

Re: GitHub issues - switching technical tasks

I would like to move it to labels. We can use a stale action to close inactive issues, pr. I found the following milestone in MCLEAN, MJLINK, ARCHETYPE with label characteristics (and I give the suggestion, if it was possible for me, how to map): next-release* -> ? (I have no idea) waiting-

Re: GitHub issues - switching technical tasks

On Mon, 13 Jan 2025 at 12:51, Sandra Parsick wrote: > > > Please check, is there a space after ":" > > > > "priority: major" - > "priority:major" > > > > as defined in: https://github.com/apache/maven-gh-actions-shared/pull/129 > > > Thanks for the catch. I fixed it. > > > I did a new test run wit

Re: GitHub issues - switching technical tasks

Please check, is there a space after ":" "priority: major" - > "priority:major" as defined in: https://github.com/apache/maven-gh-actions-shared/pull/129 Thanks for the catch. I fixed it. I did a new test run with all the new configuration fixes. Another thing that I recognized: Some miles

Re: GitHub issues - switching technical tasks

On Mon, 13 Jan 2025 at 08:51, Sandra Parsick wrote: > > > Then I think we should use a PR reference instead of a simple link. > > Do you see a problem I did not expect? > > I'm fine with that. I have to think about the testing because I cannot > use the original Jira project because a test run wou

Re: GitHub issues - switching technical tasks

Then I think we should use a PR reference instead of a simple link. Do you see a problem I did not expect? I'm fine with that. I have to think about the testing because I cannot use the original Jira project because a test run would trigger new events in the original PR. This would be a waste.

Re: GitHub issues - switching technical tasks

Le dimanche 12 janvier 2025, 09:50:28 CET Sandra Parsick a écrit : > >> > >> > > > > It appears that link to an external sources have a separate datatype. > > Therefore, the migration tool ignores it. I will fix it (see issue [1]). > > > > I solved this issue. I added a new text in the body. Ple

Re: GitHub issues - switching technical tasks

It appears that link to an external sources have a separate datatype. Therefore, the migration tool ignores it. I will fix it (see issue [1]). I solved this issue. I added a new text in the body. Please check it if it is good enough. [1] It is possible to add a PR reference to the GitHub

Re: GitHub issues - switching technical tasks

I think having the possibility to give issues / PR a priority ist very useful in a environment like Maven - but should only be doable by maintainers (as all labels, except the auto labels when using the issue template). Btw labels: I like it very much, that the label for newcomers is called "good

Re: GitHub issues - switching technical tasks

Should we need to map a priority from JIRA to GitHub issues - it can be useful information. If so, we can add labels like - https://maven.apache.org/developers/conventions/github.html#Priority On Fri, 10 Jan 2025 at 21:51, Hervé Boutemy wrote: > > Le mercredi 8 janvier 2025, 18:50:59 CET Sandra

Re: GitHub issues - switching technical tasks

Thank you for your feedback. the only missing aspect I found is when a Jira issue links to a PR, like for example https://issues.apache.org/jira/browse/ARCHETYPE-690 the issue in GH does not display it: https://github.com/support-and-care/mvn-issues-migration-test-archetype/issues/647 with t

Re: GitHub issues - switching technical tasks

Yes, migration result looks impressive. We may ignore comments in Jira like 1) author Hudson and text inside "Build success | Build failed" 2) comments from GH bot about a comment to PR. Sylwester [image: hudson]Hudson added a

Re: GitHub issues - switching technical tasks

Le mercredi 8 janvier 2025, 18:50:59 CET Sandra Parsick a écrit : > - ARCHETYPE > > Migration result: > https://github.com/support-and-care/mvn-issues-migration-test-archetype > Used migration config: > https://github.com/support-and-care/jira-to-gh-issues/blob/master/src/main/j > ava/io/pivotal

Re: GitHub issues - switching technical tasks

Sandra, it seems modification permissions have been added for you to https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching can you edit to confirm it works, please? Le vendredi 10 janvier 2025, 16:11:26 CET Sandra Parsick a écrit : > As Hervé already mentioned, I star

Re: GitHub issues - switching technical tasks

As Hervé already mentioned, I started the list on GitHub because I didn't know where is the best place to put this kind of information. I clean up the list on GitHub and remove all duplicated information. Only the status about the migration config for the tool is stayed and some remarks, but I

Re: GitHub issues - switching technical tasks

On Fri, 10 Jan 2025 at 12:50, Hervé Boutemy wrote: > > Le vendredi 10 janvier 2025, 07:44:34 CET Slawomir Jaranowski a écrit : > > On Fri, 10 Jan 2025 at 01:59, Hervé Boutemy wrote: > > > can we have an up to date list of initial test migrations before talking > > > about large scale? > > > I see

Re: GitHub issues - switching technical tasks

Le vendredi 10 janvier 2025, 07:44:34 CET Slawomir Jaranowski a écrit : > On Fri, 10 Jan 2025 at 01:59, Hervé Boutemy wrote: > > can we have an up to date list of initial test migrations before talking > > about large scale? > > I see 2 tracking lists: > We should have one list. +1 > > All past

Re: GitHub issues - switching technical tasks

On Fri, 10 Jan 2025 at 01:59, Hervé Boutemy wrote: > > can we have an up to date list of initial test migrations before talking > about large scale? > > I see 2 tracking lists: We should have one list. All past technical task was documented on ASF Wiki on Maven space: https://cwiki.apache.org/c

Re: GitHub issues - switching technical tasks

can we have an up to date list of initial test migrations before talking about large scale? I see 2 tracking lists: 1. https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching with 8 GH Issues enabled for 4 Jira projects: MPOM, MASFRES, ARCHETYPE, MNGSITE 2 "copi

Re: GitHub issues - switching technical tasks

On Wed, 8 Jan 2025 at 21:41, Sylwester Lachiewicz wrote: > > Another thing that could be automated like labels - is the management of > .asf.yaml and README.md files for our repositories. > I see - READM.md - issues templates, PR templates and so on ... We can start a new thread about it. >

Re: GitHub issues - switching technical tasks

Another thing that could be automated like labels - is the management of .asf.yaml and README.md files for our repositories. Sylwester śr., 8 sty 2025 o 18:51 Sandra Parsick napisał(a): > I created for the mentioned Jira projects some test repositories that > show the migration result. > > > >>

Re: GitHub issues - switching technical tasks

I created for the mentioned Jira projects some test repositories that show the migration result. - ARCHETYPE There is a PR for ARCHETYPE - please review. After merge we can try to copy the issue - I don't have time to support it so please someone else to help. If we want to copy release note

Re: GitHub issues - switching technical tasks

On Wed, 8 Jan 2025 at 03:36, Hervé Boutemy wrote: > > we'll need to clarify what projects are guinea pigs, to stress test the > issues history copy > and releases/milestones > > I see 3 cited: > - ARCHETYPE There is a PR for ARCHETYPE - please review. After merge we can try to copy the issue - I

Re: GitHub issues - switching technical tasks

we'll need to clarify what projects are guinea pigs, to stress test the issues history copy and releases/milestones I see 3 cited: - ARCHETYPE - MCLEAN - MJLINK MNGSITE does not have any release, then not really something key IMHO for testing migration I see also MPOM, but it seems it has be

Re: GitHub issues - switching technical tasks

Ok be to on track I was created a wiki site - https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+switching As for our ASF MAven initiatives we use wiki to document progress and so on ... so in this case it should be the same. On Tue, 7 Jan 2025 at 17:41, Sandra Parsick wrote: > > >

Re: GitHub issues - switching technical tasks

No manual work ... I thought about not migrate issues at all for this repo - MNGSITE Ah, thanks for clarifying. I misunderstood it. We have voted about switching to GitHub ... https://lists.apache.org/thread/h42ls1ccc1flhk2yrkwc6rz05m8rjq6r I'm not going to do about 100 votes ... for each re

Re: GitHub issues - switching technical tasks

On Tue, 7 Jan 2025 at 16:56, Sandra Parsick wrote: > > I created migration configuration for the following projects : > > - MCLEAN [1] > - MJLINK [2] > - MNGSITE with a filter, so that only open issues are migrated [3] > > @Slawomir: I know that you want to migrate the issues of MNGSITE > manually

Re: GitHub issues - switching technical tasks

I created migration configuration for the following projects : - MCLEAN [1] - MJLINK [2] - MNGSITE with a filter, so that only open issues are migrated [3] @Slawomir: I know that you want to migrate the issues of MNGSITE manually. The configuration should demonstrate a possibility to migrate o

Re: GitHub issues - switching technical tasks

After a discussion with Gerd Aschemann, I moved the migration list from the Github Issue to the repository of the migration tool [1]. I adjusted the list according to already provided feedback. If someone wants to have write permission to this repository, please let me know it, I will assign i

Re: GitHub issues - switching technical tasks

On Mon, 6 Jan 2025 at 16:16, Elliotte Rusty Harold wrote: > > On Mon, Jan 6, 2025 at 8:20 AM Slawomir Jaranowski > wrote: > > > > Hi, > > > > Last time I enabled GitHub issues in https://github.com/apache/maven-site > > I don't have a plan to copy old issues for this project from jira to GitHub.

Re: GitHub issues - switching technical tasks

On Mon, Jan 6, 2025 at 8:26 AM Guillaume Nodet wrote: > > Is there any way to make the JIRA for migrated projects read-only, or > at least disable the creation of new issues ? We don't want it to be read-only prior to a full migration since many of these issues still need to be worked on. Disabli

Re: GitHub issues - switching technical tasks

On Mon, Jan 6, 2025 at 8:20 AM Slawomir Jaranowski wrote: > > Hi, > > Last time I enabled GitHub issues in https://github.com/apache/maven-site > I don't have a plan to copy old issues for this project from jira to GitHub. > Can we figure that out before we proceed with the other repos? This is i

Re: GitHub issues - switching technical tasks

First we need to enable issues on GitHub to allow migrating issues. So please add a column "GitHub Issues enabled" Thanks for the feedback. I added another column. I'm still not sure if we need to copy issues for all projects - up to you. My preferred way is to migrate all issues for all pr

Re: GitHub issues - switching technical tasks

On Mon, 6 Jan 2025 at 13:15, Sandra Parsick wrote: > > Hi, > > I created an overview about the Jira Project that are Maven related (I > used the project category 'Maven' and ignored retired projects) [1]. > > I will start creating migration configuration based on that list. Do you > have prefered

Re: GitHub issues - switching technical tasks

Hi, I created an overview about the Jira Project that are Maven related (I used the project category 'Maven' and ignored retired projects) [1]. I will start creating migration configuration based on that list. Do you have prefered order? Did I miss any projects? - Sandra [1] https://github

Re: GitHub issues - switching technical tasks

On Mon, 6 Jan 2025 at 09:26, Guillaume Nodet wrote: > > Is there any way to make the JIRA for migrated projects read-only, or > at least disable the creation of new issues ? > That would help a lot in guiding existing contributors to GitHub for new > issues. > There is a ticket for infra ... htt

Re: GitHub issues - switching technical tasks

Is there any way to make the JIRA for migrated projects read-only, or at least disable the creation of new issues ? That would help a lot in guiding existing contributors to GitHub for new issues. Le lun. 6 janv. 2025 à 09:21, Slawomir Jaranowski a écrit : > > Hi, > > Last time I enabled GitHub i

GitHub issues - switching technical tasks

Hi, Last time I enabled GitHub issues in https://github.com/apache/maven-site I don't have a plan to copy old issues for this project from jira to GitHub. Now I'm working on next repo - https://github.com/apache/maven-apache-resources/pull/23 In next I will use the similar issues templates We ha