-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent creation of new issues in the WEBSITE project on Jira #3268
Comments
@jenkins-infra/jira-admins WDYT about this proposition? |
definitely block issues, that tracker hasn't been used in ages. |
Sure, if nobody looks at Jira anymore, then we should stop accepting new issues. Has anyone reviewed the old WEBSITE issues whether they should be migrated? INFRA was migrated with references to new issues, HOSTING had no open issues. |
The last one has been opened end of November, @MarkEWaite redirected it to GitHub issues via a comment already. The previous one was opened in April and the one before in December 2021. I can migrate them to https://github.com/jenkins-infra/jenkins.io/issues/ but I'm not sure if there is any value in that. |
I would not just throw them in the trash, never to be seen again. We don't need to automatically migrate everything, like was done for INFRA also for closed issues, but issues that have merit should not be lost just because we decided on a new issue tracker without a plan to deal with old issues. |
I didn't imply to delete them from Jira, just wondering about migrating them, ie copying them to GitHub and closing them in Jira 🙂 |
Right, but if we now take this action to definitely abandon the old WEBSITE issue tracker, with nobody looking at it again, we should take this opportunity to review open issues and determine which are worthwhile. "The trash" here does not necessarily mean deletion, having an issue tracker that's basically invisible is not much better. |
I think that @kmartens27 and I can review the open issues in the WEBSITE project and close them or recreate them on the www.jenkins.io GitHub repository. Query that I'm using to process the queue is https://issues.jenkins.io/issues/?jql=project%20%3D%20%22Jenkins%20Website%22%20and%20status%20not%20in%20(done) |
I've made a first sweep through the website issues, closing those that I thought were no longer relevant or that I could fix quickly. Still 100 issues that need review by @kmartens27 for prioritization and further discussion |
I have started reviewing the issues that @MarkEWaite was referring to, and will be discussing with him further for what should be transferred. |
I see this list is now empty 🎉 @MarkEWaite @kmartens27 Is there anything remaining to do related to this issue or could it be closed as completed? |
@lemeurherve I believe this can be closed as completed. The tickets that are still relevant have been migrated to GitHub issue tracking, and all the WEBSITE tickets have been closed. |
Should be done, please confirm. |
Confirmed, thanks! |
Service(s)
Jira
Summary
The website components use GitHub issues as tracker, as integrated on jenkins.io footers, e.g., yet people raise new Jira issues sporadically.
I'd recommend we do the same we did to the HOSTING project, remove the WEBSITE project from the issue creation dropdown form.
That will leave all issues as-is, but prevent the creation of new issues on Jira.
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: