Looking for options on public facing issue creation

Question

Hi!

Looking for options on public facing jira issue creation without login. I was looking into issue collectors but I would prefer a non-code solution.

Ultimately the goal is for the team to submit tickets for the dev team to review. These tickets can be bugs, enhancement, new features.

Let me know!

Thanks

Nic Brough -Adaptavist- · Answer

Oh, and this sort of thing might lead you to Jira Product Discovery too - I don't know how the licence model might work, but I imagine it will be similar to the "free customer" model, to allow you unlimited numbers of people to contribute towards your roadmap!

padraik · Answer

The only thing I can think of is to try using a mail handler.

Create issues and comments from email

Nic Brough -Adaptavist- · Answer

The Jira Service Management option might be worth considering, but it's a different model to "create issue for developers".

The idea there is that a "customer" would create requests (anonymously if you want, but as "customer" accounts are free, I would recommend not - it's better to be able to interact with the customer for whom you have some contact details and it redices the risk of spam ).  These spawn issues, which your "Agents" work with.

Think of those issues as routes of communication, not stories for your developers.

When someone raises a bug, feature, support request, etc, your Agents will do a bit of triage - you might already have documentation you can refer them too, or you've got a bug fix coming in a couple of weeks, or it's on the roadmap, etc.

When the Agent thinks "yep, ok, this is a new thing that needs to go to development", then they can use "create linked issue" to create a story in the right project, with probably lots more info than just what the customer said, and then track it through the dev process, reporting back to the customer as needed via the request.

Agents are expensive Jira users, but because they will be sending (well formed, non-duplicate) issues to developers rather than doing it all themselves, you don't actually need many of them.

A lot of places use models like 50 developers, 3 Agents.  3 Agents are free! (and the Agents can double as developers if you want)