Issue/consistent object naming

KarlPatach / SalesforceGitVisualiser

This project is a first step in integrating GitHub into Salesforce. Its vision is enabling developers to have a single consolidated view of all the projects they are working on or are interested in, directly in Salesforce, with tight coupling with standard Salesforce objects such as Users, Cases and Work Items (available in Agile Accelerator app).

2 stars 0 forks source link

Issue/consistent object naming #17

Closed KarlPatach closed 4 years ago

KarlPatach commented 4 years ago

Fixes #16

KarlPatach commented 4 years ago

Converted to draft as there are still a few setup issues (e.g. validating and syncing will create new objects instead of mapping to existing ones)

pozil commented 4 years ago

Ok, if you go down that path, it could be interesting to check if you can create relationships between the external objects: Repo -> PR Repo -> Issue

Disclaimer: I don't know what's required to achieve that. Perphaps it's for a dedicated PR...

pozil commented 4 years ago

Relationships would allow us to do proper reporting on multi-objects.

KarlPatach commented 4 years ago

I think this will be done in at least one other PR. Btw I will create a new issue for Issue-->user relationship that has been broken in a previous PR (syncing the external object reseted this setting)

KarlPatach commented 4 years ago

Sorry for the number of files @pozil 😅 Renaming one object meant modifying like 10 files at a time...