The issue template is so complicated that PO decided to redo in fibery
Next time we should test it with a user. Lots of things don't make sense, you can't say "same experiences as digipower live", it warns you the issue is public, but it still asks you for a password, you have to create another issue for the aggregate bubble etc...
General Context
FIRST STEP: add linkedin to digpower live participant bubble
then model asdpo on the digipower bubbles
asdpo-participant asdpo-aggregator
Bizdev Contact Person
@pdehaye
Deadline / Importance
tomorrow
Bubble Title
Swiss DPO association
Bubble ID
asdpo-participant
Bubble Description
No response
Additional Content
No response
Icon URL
https://asdpo.swiss/wp-content/uploads/2019/03/DPO_Template.jpg
Bubble Type
Participant
Destination Bubble(s)
No response
Additional Destination Bubble(s)
asdpo-aggregator
Consent Form
same as digipower live
⚠️ Codeword
No response
Public Key
9829898375f98cd3e202bfdd9924e9c449e85e3adba2802a88e16de44f29aa24
Experiences
linkedin
Custom Data Sources
No response
Custom Set of Views
No response
Other customisations
No response
Anything else?
The issue template is so complicated that PO decided to redo in fibery
Next time we should test it with a user. Lots of things don't make sense, you can't say "same experiences as digipower live", it warns you the issue is public, but it still asks you for a password, you have to create another issue for the aggregate bubble etc...
The form should fit on one screen ideally