Hi,
for our upcoming computer game we want to integrate an inbuild bug / feature request form. We thought using Asanas form capabilities would be a perfect fit because then we wouldn’t need to import the tasks later into Asana.
We had a quick look at how the web request works when submitting the form and it seems straight forward (POST against submitForm?id=… with the tracked payload structure). However: We are not very certain that this feature is intended to be used that way and will be stable over a longer period of time. We didn’t find an API documentation for app form submissions or something like that. And if we understood correctly creating tasks via the “normal” API would require a logged in Asana user (which our players aren’t).
Any hints would be appreciated.
Best regards
Bennet
Hi @Bennet_Jeutter,
You are correct - Forms are not currently available via the API, and what you describe isn’t officially supported or endorsed. That said, you could do it if you want, so long as you accept that it might break at some point (but it might not!).
2 Likes
Thanks for the quick reply! Since I don’t really like the idea of the reporting breaking at some point i’m evaluating other options. I’d like to use a guest account who creates new tickets. We would use POST /tasks with the respective guest token then.
Is there any way to limit the guest user to only be able to create new tasks and not seeing already created tasks? I’m worrying about someone with skills taking the auth token and - at least - being able to retrieve the customer ticket backlog (since invited to that project).
No, sorry, there’s no access option that would do that.
Okay, would be cool to see something like this in the future. For now I created a little proxy web service which then talks to Asana API (so the end users aren’t able to get the token and do unwanted stuff with the API).
1 Like
The game is called “Indoorlands”.
Integrating an in-game bug/feature request form with Asana’s form capabilities can indeed streamline the process and eliminate the need for manual task imports. Here’s a general approach to achieve this:
- Create an Asana Project: Set up a project in Asana specifically dedicated to collecting bug reports and feature requests for your game.
- Create a Form in Asana: Within the project, create a form using Asana’s built-in form feature. Customize the form fields to capture relevant information like title, description, priority, category, and any other details you require.
- Generate Form URL: Once the form is created, Asana will generate a unique URL that can be used to submit entries.
- Integrate Form in the Game: In your game, design a user interface that allows players to access the bug/feature request form. Provide a button or menu option that, when clicked, opens a web browser or a web view within the game itself.
- Open the Form: When the player interacts with the form button/menu option, it should open the Asana form URL in the web browser or web view. Players can then fill out the form fields to submit their bug reports or feature requests.
- Handle Form Submission: Once a player submits the form, the data will be recorded in Asana’s project. You can configure notifications or assignees in Asana to receive updates about new submissions.
- Review and Process Submissions: Regularly review the bug reports and feature requests in the Asana project. You can assign tasks, prioritize them, add additional details, and track their progress directly within Asana.
By implementing this approach, you can seamlessly collect bug reports and feature requests from within your game environment and have them directly recorded in Asana for your team to review and address. Remember to customize the form fields and project settings in Asana to align with your specific requirements.