Difference between revisions of "Jira"
(→Strategy: database isn't needed; link script) |
(→Not yet archived: https://bugs.openjdk.org/) |
||
Line 37: | Line 37: | ||
https://jira.ecmwf.int/ | https://jira.ecmwf.int/ | ||
https://jira.atlassian.com/secure/Dashboard.jspa | https://jira.atlassian.com/secure/Dashboard.jspa | ||
https://bugs.openjdk.org/ | |||
</nowiki> | </nowiki> | ||
Revision as of 06:06, 6 February 2024
Jira is a bug tracking system developed by Atlassian. They previously offered a self-hosted version (Jira Server), but have ended sales on Feb 15, 2023[1] and support will fully end on Feb 15, 2024,[2] leaving the only options as their cloud version[3] or the comically expensive data center version.[4]
Strategy
An ArchiveBot !a command will not properly discover all issues.
The approach I've used is to find the highest-numbered ticket in each project (use the "all issues" filter and order by "key"), and then generated a text file listing all of the ticket URLs, which then can be ran (by an op) as an !a < list job.
Attachment mime types do get detected as a relative URL, and will need to be ignored, along the lines of https://example.com/browse/(application|text|image|video)/
. This logging also includes the attachment URL (incorrectly detected as a relative URL), which is sufficient for extracting attachments from the log (they won't be saved with an !a < list job due to the no-parent rule, but the database is not needed). Additionally, attachment sorting is not useful to save, so [?&]attachment(Order|ViewMode|Sortby)=
can be ignored.
Issue comments are loaded via JS and are not properly saved. However, all comments are included when exporting an issue in "printable" form, as well as in the XML and DOC export formats. As such, these export links are worth saving (though they either need to be generated as a list or extracted from the job's database). https://example.com/si/jira.issueviews:issue-html/PROJ-12345/PROJ-12345.html
https://transfer.archivete.am/sSx9w/jira_url_list.py generates a list of URLs, also using the Jira API[IA•Wcite•.today•MemWeb] to determine the maximum issue for each project.
Status
Not yet archived
Move URLs to the next section when done. This list is very much incomplete.
https://bugreports.qt.io/ https://jira.anuket.io/ https://jira.fd.io/ https://jira.lfnetworking.org/ https://jira.linuxfoundation.org/ https://jira.onap.org/ https://jira.opendaylight.org/ https://jira.hyperledger.org/ https://jira.automotivelinux.org/ https://issues.freepbx.org/ https://tracker.moodle.org/ https://issues.apache.org/jira/browse/ https://ugene.dev/tracker/ https://jira.mongodb.org/ https://issues.redhat.com/ https://jira.ecmwf.int/ https://jira.atlassian.com/secure/Dashboard.jspa https://bugs.openjdk.org/
Archived
Move URLs here when they are started/done.
https://bugs.mojang.com/ https://hub.spigotmc.org/jira/