Adam Setch

Ditto - I find that this feature would be incredibly helpful, particularly when using tools like DependencyTrack to visualize the dependency graph. Trivy has support for maintaining dependency relationships

@hughlilly @JakeSidSmith - can you please re-test on [v4.4.0](https://github.com/gitify-app/gitify/releases/tag/v4.4.0).

Thanks @bquorning - interesting - I wasn't able to reproduce on `main` Sonoma 14.4. For now I'll re-open this ticket. Would you mind sharing a brief recording / gif recreating...

@bquorning - we just released v5.0.0. If you have a moment, could you kindly retest with this version and share your experience

> I haven’t seen the issue since upgrading to v5.0.0 last week. Thank you 🙏🏼 Great news. Thanks for confirming @bquorning

Perhaps we could also move eclipse-temurin:8 into it's own packageRule underneath the existing `javaLTSVersions`workaround, so that we can tweak the `allowedVersions` expression to match the specific format.

Earlier today my Lead iOS Engineer raised this as being a useful feature addition to our Renovate workflow. Is there any pre-req items I should be aware of for this...

> ideally this feature is platform independent, so the code should not reside inside bitbucket platform. > > maybe it can reside inside `modules/issues/jira`, so we can later extend it...

> i think we should only support a single Jira target project, which should be configurable when not determined from platform. Agree to limiting to a single Jira target project...

@devansh-sharma-tw @naveengenupuritw - appreciate your feedback re this feature proposal