If using repo integrated with JIRA, the JIRA issue is usually mentioned in branch, like feature/MYJIRA-123_feature_name.

To use integration with git bug be nice to be able to import only needed issue(parsed from branch, or choesen manually somehow), not all 1000.

Thanks for great product

This was mentioned in https://github.com/MichaelMure/git-bug/pull/241

One possible solution would be to use git-bug's query language to define import filters.

Michael Muré (MichaelMure) added label area/bridge 5 years ago

Michael Muré (MichaelMure) added label enhancement 5 years ago

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

sudoforge added label area/bridge/jira 1 year ago

sudoforge removed label area/bridge 1 year ago

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

sudoforge removed label enhancement 1 year ago

sudoforge added label kind/feature 1 year ago

sudoforge added label priority/awaiting-more-evidence 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/stale 1 year ago

Not stale

On Sun, Nov 3, 2024, 4:28 AM github-actions[bot] @.***> wrote:

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.

— Reply to this email directly, view it on GitHub https://github.com/git-bug/git-bug/issues/374#issuecomment-2453278856, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACH6DLRLKMP3GXQBHGVIL3Z6WJ5XAVCNFSM6AAAAABLJPUFJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGI3TQOBVGY . You are receiving this because you commented.Message ID: @.***>

github-actions (github-actions) removed label lifecycle/idle 7 months ago