Open nkylstad opened 1 year ago
Beware that some app developers are used to forking apps from their org and down to their own user accounts, and then open pull requests back to the app repo in the org account. That means that when they open the app in Studio/designer, they point to their own copy of the app, not the org one. Re-using resources should probably also work in those cases, or whenever you copy an app to a user (or even a different org?).
Hmm interesting point! Might branching support be a way to solve this instead? So that they can create branches from the org repo, rather than forking the app to their own users?
Alternatively we could look at ways to find which orgs a user has team membership for, and allow for import of shared resources from those orgs.
Yes, and yes! :raised_hands: I don't have preferences for how this should be solved, I just noticed a possible pitfall when hearing about this in the roadmap discussion last week. :blush:
Description
Many organizations have a set of texts that they use across multiple appplications. It should be possible to import shared texts when working on an app. These texts could f.ex be from the organization, or even standard texts provided by Altinn Studio.
We should also support export/import of texts to other formats.
In scope
Out of scope
Additional Information
The solution should be generic enough that it should be simple to add Altinn standard texts as well.
Dependencies
Issues