Defining Survey Template

Publishing Survey Template

View Reports

Easily create and publish your surveys with the questions you want. Users can be asked to enter their own replies as free text for the questions which can be defined as mandatory or optional while adding.

Publishing Survey means to create assignment of survey template. Publishing supports Roles based, Group based and user based assignments. All assigned users can be notified about the specific publish.

You can view report by publication or survey template. Reporting by publication also has showing users who completed or not. You can also download csv of report.

Is there a way to lock down who can generate templates and view reports on these surveys? Preferably locking down by using either users or groups. We would ideally just want our JIRA users to just take a report and not view the results or create their own.

This plugin is exactly what we needed to receive valuable customer feedback. It is very flexible, easy to configure, and allows us to choose when in the workflow the survey will be sent. The survey itself is also easily customizable. The only feature I would like to see is to be able choose what date a survey is sent.

As Yasinne comments, this plugin doesn't connect with Customer Users, so our customer won't be able to fill up a survey. Beside that, is there chance to get the survey from a trigger event in the workflow? Maybe when an issue is resolved, cancelled, etc?
I look forward to get the new version :)

Thank you for testing out our plugin. We have the capability that admin can configure his/her workflow to assign survey to reporter via the postfunction. Also we are working on a centralized management of the triggering. Do you mind sending further details to david.lindstrom@jirasurvey.com?

Is there a way to lock down who can generate templates and view reports on these surveys? Preferably locking down by using either users or groups. We would ideally just want our JIRA users to just take a report and not view the results or create their own.

This plugin is exactly what we needed to receive valuable customer feedback. It is very flexible, easy to configure, and allows us to choose when in the workflow the survey will be sent. The survey itself is also easily customizable. The only feature I would like to see is to be able choose what date a survey is sent.

As Yasinne comments, this plugin doesn't connect with Customer Users, so our customer won't be able to fill up a survey. Beside that, is there chance to get the survey from a trigger event in the workflow? Maybe when an issue is resolved, cancelled, etc?
I look forward to get the new version :)

Thank you for testing out our plugin. We have the capability that admin can configure his/her workflow to assign survey to reporter via the postfunction. Also we are working on a centralized management of the triggering. Do you mind sending further details to david.lindstrom@jirasurvey.com?

Pricing

Paid-via-Atlassian pricing FAQ

How does server app pricing work?

Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

How do I determine my server pricing?

Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

Do you offer academic, community, or open-source licenses?

For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

How can I buy apps for my legacy Jira Server or Confluence Server license?

If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

Purchase the app at the non-legacy Unlimited (10000+ users) tier.

Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.