Hello! I was looking into this and thought it would be great to integrate one of my repos with an Epic that is in my team's Jira Project. However, I don't see a way to filter or import a subset of a project. Our team maintains a dozen different repositories, so git bug bridge pull would be pretty excessive to sync our thousands of Jira tickets for each repo.

Is there an idea or a PR or docs behind how you could do partial import/export syncing in Jira to just tickets under an epic? I was thinking the simplest would be just some kind of interface to JQL, but it looks like it's hard-coded and I'm not sure if that's the only place that this is happening or if there's some other config that I am missing.

This has been discussed indeed (see https://github.com/MichaelMure/git-bug/pull/241), but that will require someone to actually implement it.

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/rotten 11 months ago

github-actions (github-actions) removed label lifecycle/stale 11 months ago

sudoforge removed label lifecycle/dormant 7 months ago