Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do portal customers vote on issues? Edited

I must be missing something simple. Using organizations I can make issues visible to customers but they have no access beyond commenting. They can't vote.

There is zero point in our small team voting on issues. We need customer votes.

There is a voting and feedback plugin but it doesn't change the existing votes. It uses custom fields.

There is a feature request from 2015 (with 380 votes) but that was five years ago.

Is there any way to allow a portal customer to vote?

Customers - voting.png

3 answers

1 accepted

0 votes
Answer accepted

Customers don't get access to the issues behind their requests.

Voting is not something a service desk is expected to do - the core purpose of a service desk is for requesting help, change or bug fixes.  It's not intended as a product management system.

Customers are automatically watchers on the requests they raise, so generally you don't need them to watch issues.  If you do need customers to be notified on other people's requests, you'll need them to be added as participants (which the requestor or agents can do).  You can't get them into the "watchers" on the issue because they have no access to the issue.

Thanks for the explanation. Do you know if there is an Atlassian product, which does allow this without the need to buy user licenses for an unknown number of external customers?

- the core purpose of a service desk is for requesting help, change or bug fixes.

Finding existing changes or bug fixes and voting them into action would greatly assist this core purpose and save the customer from duplicating the request as I've done here.

A perfect solution would be to find and present existing issues as they type. Confluence Knowledge Base behaviour for issues would make the Atlassian Service Desk shine. ;-)

I'm not aware of any app that could enable this

If you do need customers to be notified on other people's requests, you'll need them to be added as participants (which the requestor or agents can do).

This is something where the customer should be in control. When would a customer ever want someone else to add them to an issue? If I see an issue and would like to be notified about changes, that's a decision for me, not for someone else. This is how it works in the screenshot from the Atlassian site.

Like Selva likes this

Issues, I'm with you.  I'm less sure on watching other people's requests.  Why would I want to watch other people's requests?

Note - not issues, requests...

Type of issue shouldn't matter. Request, bug, support, question, feature, improvement, anything.

Sharing it should be something enabled in the back-end for any type of issue. Organisations don't really work for me. I think it confuses the customer to have this option when submitting.

I'd prefer a share with portal customers option on a service desk or software issue. From there, any customer can see the issue in their search and watch or vote or comment. Manually adding every customer to a global organisation just to share an issue is bizarre.

Service desk - Organisations.png

I think you're missing the difference between a service desk and an issue tracker here.

Consider the usual service desk use-cases - imagine you're a banking client or a software end-user who has bought software - that's a very different use-case to "items-needing-work issue tracker"

You're right but the licensing is forcing my hand. I'd rather expose selected issues from the tracker to my customers the same as Atlassian but this isn't an option due to costs.

I'm stuck with coercing the service desk into managing access.

I can't understand why they allow anonymous access but not customer access.

It's a shame because I've moved everything into production but I'm yet to make a decision on how to handle this.

Oh wow! I've just noticed the feature request has changed to "In progress". This has occurred since my screenshot from yesterday. Thank you! You've made my week a lot brighter!

That's good.  I've re-read my answer and realised I was explaining why it's not there yet (Atlassian's original model of a helpdesk), and missed out that I think it should be added because people are using heldesks to gather feature requests where voting can be useful.  I went to that feature request and found I'd already voted for it!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

182 views 1 6
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you