Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reuse integrations from across apps #705

Open
kitallis opened this issue Dec 23, 2024 · 2 comments
Open

Reuse integrations from across apps #705

kitallis opened this issue Dec 23, 2024 · 2 comments
Labels
gitstart tickets for GitStart to pick up

Comments

@kitallis
Copy link
Member

kitallis commented Dec 23, 2024

Context

We previously allowed reusing integrations across categories in the same app. See #255.

But sometimes, access to things like Slack are human-firewalled heavily in big orgs, so to avoid bureaucratic delays, it's easier to reattach integrations from another existing app on Tramline (along with reuse from existing app, which already exists).

Requirements

We now want to allow users to reuse integrations across apps. The integrations should be reusable both across apps and across categories. For example,

App 1:

  • VCS: GitHub ✅
  • Build Servers: Bitrise ✅

App 2:

  • VCS: [Reuse from App 1, GitHub] 🔁
  • Build Servers: [Reuse from App 1, Bitrise] 🔁

App 3:

  • VCS: GitHub
  • Build Servers: GitHub ✅
  • Notifications: Slack ✅
  • Build Distribution: Play Store, Firebase ✅
  • Monitoring: Bugsnag ✅

App 4:

  • VCS: [Reuse from App 3, GitHub] 🔁
  • Build Servers: [Reuse from App 3, GitHub VCS] 🔁
  • Notifications [Reuse from App 3, Slack] 🔁
  • Build Distribution: [Reuse from PlayStore, Reuse from Firebase] 🔁
  • Monitoring: [Reuse from Bugsnag] 🔁

Compatibility

  • Cross-app, cross-category is also possible, for example I can connect a VCS integration to Build Servers, but only for certain integrations and certain categories (elaborated later)
  • All integration categories across apps are re-usable (not just build servers)
  • The configuration of each integration will still be done per app, that will not get copied over

Cross-app, cross-categories

Only GitHub can be shared cross category. The rest can only be shared within their categories for now. These things should be configurable with hashmaps/code to extend later.

Acceptance Criteria

The interface will look something like this:

There will be 2 buttons, one to immediately reuse from existing app (like we have right now), the other one will only show when there is more than one app with connected integrations that can be used.

On click on that button, a modal will pop-up and list the integration options, with the following content:

  • Integration name & icon
  • installation id (or some identifier)
  • app bundle identifier that it belongs to

The user will select one, and save.

Additional Notes

N/A

@kitallis kitallis added the gitstart tickets for GitStart to pick up label Dec 23, 2024
Copy link

Issue synced into GitStart. Please review, edit and hand it off to GitStart by following this link.

Copy link

This issue has been handed off to GitStart: https://clients.gitstart.com/tramline/11653/tickets/TRAB-705

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gitstart tickets for GitStart to pick up
Projects
None yet
Development

No branches or pull requests

1 participant