We could try something like this:
https://github.com/hbrands/jira-issues-importer
Both projects have APIs...
--
The Apache Software Foundation
V.P., Data Privacy
On Fri, Nov 24, 2023, at 19:37, Matt Sicker wrote:
> I’d like it if we could copy over open issues to GH.
> —
> Matt Sicker
>
>> On No
I’d like it if we could copy over open issues to GH.
—
Matt Sicker
> On Nov 24, 2023, at 07:12, Piotr P. Karwasz wrote:
>
> Hi all,
>
> Since we switched to Github Issues, I rarely look at JIRA any more and
> certainly I do not expect to see new issues being posted there.
>
> Should we ask INF
Hi Ralph,
On Fri, 24 Nov 2023 at 16:50, Ralph Goers wrote:
>
> We should NOT be creating new Jira issues. But locking down Jira completely
> would mean we would have to somehow transfer any active issues to GitHub.
> When that happens I would expect the Jira issue to link to the GitHub issue
>
We should NOT be creating new Jira issues. But locking down Jira completely
would mean we would have to somehow transfer any active issues to GitHub. When
that happens I would expect the Jira issue to link to the GitHub issue and vice
versa as I would not expect all the Jira content and history
Hi all,
Since we switched to Github Issues, I rarely look at JIRA any more and
certainly I do not expect to see new issues being posted there.
Should we ask INFRA to disable issue creation on JIRA for LOG4J2? Do
we need a vote for that?
Piotr
