61
Customers have installed this add-on in at least 61 active instances.
    by //SEIBERT/MEDIAAtlassian Verified
    //SEIBERT/MEDIA is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Server 7.0.0 - 7.3.8
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.
    Supported
    //SEIBERT/MEDIA supports this add-on.

    Get support

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.

    Allow customers to view requests created by other customers belonging to the same organisation using the Customer Portal

    Allow customers to view requests created by other customers belonging to the same organisation using the Customer Portal

    Assign Groups to Units & create your own structure

    View your Unit's Service Desk requests

    ...or view your JIRA Group's Service Desk requests

    Build up the ideal structure for your special needs by assigning JIRA Groups to Units. Those Units could be companies, organisations, teams, departments or whatever you want.

    With our all new Units we empower you to put different JIRA groups into a bigger group called Units. A Unit Member can then view all the Unit's Service Desk requests.

    Of course you can also rely on your existing JIRA groups if you want. A JIRA group member can then view all the JIRA group's Service Desk requests.

    More details

    Allow customers to view requests created by other customers belonging to the same organisation using the JIRA Service Desk Customer Portal.

    This solves JSD-270

    Build up the ideal structure for your special needs by assigning JIRA Groups to our brand new Units. Those Units could be companies, organisations, teams, departments or anything you want. All members of a Unit can view the requests among each other.

    Already have all your customers in separate groups and you don't want to create new Units? No problem!

    Simply create a custom field (type: single group) & name it "Participant Group". If a customer creates a JIRA Service Desk request, our Plugin checks for the first JIRA Group he is in, and automatically adds all the members of this group as participants.

    No need for the Service Desk Customer to add manually a group or a Unit the plugin does the job.

    User reviews

    (1)
    Sign in to write a review
    by Brent Kaur on 2016-10-20
    This is exactly what we were looking for and it works like a charm. The new added features were very important to us and I can only recommend this plugin. However you have to read the manual very carefully.
    Was this review helpful?YesNo

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons 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 add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Note: While this add-on has features specific to JIRA Service Desk, the add-on 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 add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more

    //SEIBERT/MEDIA is an vendor, committed to providing support for their add-ons at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    Find out how this add-on works.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.

    Versions

    Version 2.0.0 JIRA Server 7.0.0 - 7.3.8 Released 2016-09-29

    Summary

    New configuration for Participant Units. Caution: requires manual config update

    Details

    Now you can configure trigger groups and groups to set as participants for a Participant Unit.

    JIRA Trigger Groups:The plugin tries to automatically determine the Participant Unit based on the reporter. It checks whether the reporter is in a trigger group of a unit. As soon as a unit where the reporter is member of a trigger group is found, the unit will be added to the custom field.

    Select Participants:Define groups whose members should be added as participants in an issue when the unit is selected.

    Caution!:

    This Change in the Participant Unit configuration requires an manual update of your current configuration. You must update the settings for the select participants of each unit.

    More details: Collective Issue View for Service Desk - Documentation 2.0

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Collective Issue View for Service Desk via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Collective Issue View for Service Desk. You're prompted to log into MyAtlassian. Collective Issue View for Service Desk begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Collective Issue View for Service Desk versions compatible with your instance, you can look through our version history page.

    Similar add-ons