Customer Feature Request Voting (JIRA Cloud)


We have a simply problem: Our customers can currently submit new "feature requests" through our website. However, once the requests are submitted the customers have no way of seeing the feature requests that already exist and/or "voting" on the ones they like. 

In the ideal world, we would have a way for any customer (non-jira users) to see our backlog of customer feature requests that already exist in JIRA, and vote for the ones they like. 

The constraint here is that we do not want these external customers to be able to see all of our JIRA issues that we have for our development process. And these folks do not have JIRA accounts themselves. Is there a way that we can make only certain types of our JIRA issues "public" in order for people to see/vote them?

If this is not possible through JIRA/Confluence, we are open to using an external app as long as it integrates with JIRA. Or maybe, would you recommend changing our customer feature request process entirely so that it is managed 100% in another app?

Any info on this is greatly appreciated!

1 answer

1 accepted

3 votes
Accepted answer

Hi there,

if you are willing to open up your jira to the world, you can create a project for these issues and set the browse permission to 'anyone'.

That way people can look at the issues without having a jira account. It's possible to use security levels so only certain issue types would be public, but I'd close off my sensitive Jira projects completely.

If I wanted to create some automation, I'd use scriptrunner for jira to clone certain issues (comments, custom fields) from my 'secure/hidden/private' jira project.

I would not let people to vote on things without registration because that could lead to spam and alike.

I hope that makes sense, I'm happy to clarify anything if you have some questions.

Wow, thanks for such a quick, awesome reply! 

I am about 80% sure that your first recommendation is going to be our solution. The JIRA issues that are generated from the "feature request" widget on our public website are currently going into a separate project so I think we can get away with just setting that project permission to "anyone" like you said.

Do you know if doing this will open us up to some serious security concern I should be aware of? 

Krisztian Kovacs Community Champion Jan 22, 2018

Not really,

I gather your Jira is already available from anywhere (not only on site) and it doesn't have any IP restrictions.

As long as you don't allow unregistered people to interact with your issues you'll be fine. I've opened up a Jira project once for fun, got loads of spam comments.

I'm not aware of any serious threat that you'd be facing.

Let me know if you have any other questions.

P.S.: If you think I've given you a good solution, please consider accepting my answer. Cheers!

Awesome, thanks again Krisz! We've got some more thinking/testing to do on this functionality but your answers have been very helpful. Accepting it now!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,946 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you