Hey Bubblers!
I’ve attached a picture above! I’m trying to achieve an IT Support Ticket system for our Staffs Internal site. So far, I’m struggling with connecting 2 date types. Ideally, I need one data type that will act as a “Support Ticket” that the user will generate, and another data type for our IT to write updates.
In the picture you can see the first data type, above and the second below. Is this possible? Am I overthinking how easy/complex this is? I’m up for any/all ideas for how to achieve this, compared to spamming emails to users on Outlook with updates, it would be better to be central on our site!
Sounds like you want to have a datatype ‘Support Ticket’ which is a ticket submitted by a user.
Then you want to have a datatype ‘Ticket Update’ which is created by your support staff in relation to the ‘Support Ticket’.
It seems simple enough…
Each ‘Support Ticket’ will have a field ‘Ticket Updates’ which will be a list of ‘Ticket Updates’
A ‘Ticket Update’ will have a field for ‘Support Ticket’ (which will be of a ‘support ticket’ datatype - i.e. will be the ‘Support Ticket’ it is associated with), as well as fields for ‘Support User’, ‘Support Staff’, ‘Update Content’, etc.
When a new ‘Support Update’ is created you’ll need to add it to the associated ‘Support Ticket’ in your workflow.
Hey! Thanks for this,
I’ve got this far;
But can’t seem to workout how this part works? Am I suppose to add somewhere for Updates to be added when I have no updates yet or should I leave this blank?
Yes that’s right, a brand new support ticket won’t have any updates, so no need to include that field on the workflow.
Unless, that is, you count the original support message (by the customer) as a ticket update (which you might well do). In which case you’d need to create a new support ticket first (with nothing for ticket update), then create a new ticket update (with the result of the previous workflow step as the associated support ticket). Then make changes to the newly created support ticked to add the new ticket update to it’s list of updates.
Either way is fine - it just depends how and what you define as a ticket update in your application
In either case, all subsequent ticket updates would be created and added the same way…
I.e. you’d create a new update and associated it with the Support Ticket. Then you’d make a change to the associated support ticked and add the newly created update to it’s list of updates.
One approach may be to have two data types:
Ticket
Update
And then, on your Ticket data type, you can have a field called Updates which is really a collection of updates.
I have created an example app if you are interested.
https://bubble.io/page?type=page&name=index&id=support-ticket-system-example&tab=tabs-1
Thank you both, I’ve now successfully managed to implement this! (My IT guys will be excited to help test it on Monday, many thanks and carry on bubbling! 
)
