We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Create new person, company or opportunity in the UI.
When I create a new opportunity for a person in a company, I need to jump through hoops in this sequence:
Same when I am in a company card: I cannot create an opportunity or person directly from there, breaking again the flow.
Same when I am in a person card: I cannot create an opportunity or company directly from there, breaking again the flow.
This is a poor, non intuitive workflow to me; this is a productivity drag and I feel I am fighting against the app each time I create new entities.
The current approach forces me in a basic, crude CRUD https://en.wikipedia.org/wiki/Create%2C_read%2C_update_and_delete way to deal with records based on the app data model in the backing postgres tables and not based on how I work.
When I create a new person, company or opportunity, I want to create related company/person/opportunity in-place in the card or list.
The text was updated successfully, but these errors were encountered:
I agree this is painful when using the app
Sorry, something went wrong.
No branches or pull requests
Scope & Context
Create new person, company or opportunity in the UI.
Current behavior
When I create a new opportunity for a person in a company, I need to jump through hoops in this sequence:
Same when I am in a company card: I cannot create an opportunity or person directly from there, breaking again the flow.
Same when I am in a person card: I cannot create an opportunity or company directly from there, breaking again the flow.
This is a poor, non intuitive workflow to me; this is a productivity drag and I feel I am fighting against the app each time I create new entities.
The current approach forces me in a basic, crude CRUD https://en.wikipedia.org/wiki/Create%2C_read%2C_update_and_delete way to deal with records based on the app data model in the backing postgres tables and not based on how I work.
Expected behavior
When I create a new person, company or opportunity, I want to create related company/person/opportunity in-place in the card or list.
The text was updated successfully, but these errors were encountered: