You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We ask for a lot of info on products. mediums, purposes, methodology, steps, completion description.
These 5 fields are asked for for every book & language (engagement) in the project.
My understanding is this are basically always the same for a project, and only rarely do these differ between products in the same project.
As we continue to move off of the PnP and into UI exclusively this can get really tedious.
I suggest we create a way to set product defaults at the project level.
User flows could look like:
first product in project ->
a) create product
b) create product & set as default for project
edit defaults somehow ->
a) save (will apply to new products)
b) save & apply to all existing products missing these fields
c) save & apply to all existing products overriding their current values for these fields
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We ask for a lot of info on products. mediums, purposes, methodology, steps, completion description.
These 5 fields are asked for for every book & language (engagement) in the project.
My understanding is this are basically always the same for a project, and only rarely do these differ between products in the same project.
As we continue to move off of the PnP and into UI exclusively this can get really tedious.
I suggest we create a way to set product defaults at the project level.
User flows could look like:
Beta Was this translation helpful? Give feedback.
All reactions