Using Forms as Internal ticket system for project requests

what about just setting an automation to export it everyday as an EXCEL file and upload it somewhere else?

That’s a few too many extra steps, thanks for the suggestion though.

So sorry! I didn’t see this - yes, you’ll need to be an admin in order to set that up!

@brazenTasks Hi Marlon, I agree with you this would be very helpful. I have the same use case and have already set up automated emails that are sent to the requestor with the item ID, item name, description, everytime the status changes =

  • Status “New” = email confirming successful submission
  • Status “Under review” = email updating that we have started to work on it
  • Status “Approved”/“Rejected” = email updating about the final decision on the request.

You can decide to set pretty much everything as a content in these emails.

However, I agree, requestors should be able to view whenever they want all their “open” tickets, their statuses, discuss in the update section, etc… I tried to have a “View tickets board” (this board is shareable) connected to the board where the form is (this one is not shareable)… The thing is every requestor will be able to see all the tickets and for us it’s an issue. But I think it’s not for you?
If it’s not, I think this “Board permission” set up for the “View tickets board” might be a solution for you:

Hi Ingrid,

Thanks for sharing this. Yes, I set up something very similar to what you describe for status updates. I did it a little while ago based of the other suggestions here but forgot to update about that.
It has sufficed for now. I shared details with those in my org who have access to Monday to see the board itself too since the information is not secret for anyone in the company.

It would be a helpful improvement to have a board template that creates a board of open requests or something similar, that is publicly viewable. But for now, the implemented solution is passable.