Allow restriction of PDF export views to users, user groups, roles and JQL filters

Avatar
Levente Szabo
Follow

PDF view restriction feature, similarly to the Server version.

Have more questions? Submit a request

8 Comments

Date Votes
  • 1
    Avatar
    Arnold Oyola

    Background: We are new Jira users with a modestly sized development team and on a start-up budget. We develop medical devices with stringent requirements for documentation by specific team members, thus the need for PDF exports.

    We are looking to expand our tool set. We will roll out Jira to two distinct groups (developers and planners). The former and larger groups will likely only use Jira's Kanban and tracking features. The latter group will organize work, issue reports, document progress, and is the group that generally would benefit from PDF Export. This is also the group that is most sensitive to the tools selected for the work, and has decision authority on purchases.

    We eagerly await to hear progress on this issue :)

     

     

     

  • 1
    Avatar
    Rob Mosher

    This would be incredibly helpful. Not sure if it's intended in the 'etc' portion, but limiting by project would be a great option as well. Thank you.

  • 0
    Avatar
    Ben van den Berg

    Further to the above, when a user clicks on the "Export this issue to PDF ->" link, the Export to PDF dialogue should show only the entries in the PDF View that are associated with a specific ISSUE TYPE.

    In other words, if the issue type is, e.g. Epic, story, task or bug, and there is a specific entry in the PDF views that are associated with the Epic issue type. Only that option should appear as a generatable document when the user opens an epic.

    It would be great if the configuration options for the PDF views, can offer the possibility that one or multiple issue types can be selected or unselected and the opportunity of the issue meeting the criteria of a JQL statement.

  • 0
    Avatar
    Clint Cambier

    After contacting support we received the link to this suggestion.

     

    We currently do not move forward with the purchase of this plugin as we wish to restrict who can see the actions / functionality.

    Once this is available we will evaluate again whether this plugin, at that time, still fits our needs.

     

    • We have for example 40 Jira users
    • We pay the license at the same user tier for Better PDF
    • We only want to expose Better PDF functionality to let’s say 25 specific users

     

    PS: as discussed via mail, we understand that the license has to be paid according to the user tier of our Jira instance. That is fine.

  • 1
    Avatar
    Stefano Cerio

    For starters, it would be just fine being able to manage global AND project authorizations for your app.BASIC implementation that if were you, I would have done yesterday.
    Afterwards, being able to restrict access to specific PDF Views, would be great!
    Imagine a project manager that cannot allow all his colleagues to print all kind of documents with your app! Instead he needs settings for restricting PDF export views to users, user groups, roles and JQL filters. Currently he cannot use your app. Thanks for your hard work!Love from Italy. Stefano

  • 1
    Avatar
    Stefano Cerio

    Showing all my views for all the issue types and projects in a jira instance is a mess. we created specific views that work with certain issue types or projects only - it is not only useless but creates confusion for my users showing those views where they are not needed.

  • 0
    Avatar
    Ben van den Berg

    This simple function was requested over five years ago. Could Madori please evaluate it and assist us by implementing it? This will make a huge difference to the usability of the Better PDF exporter.

  • 0
    Avatar
    Agnieszka Studniarz

    Hi, 

    I have many different templates Better PDF 
    And for our company it is very important that peole could see templates designed exclisively for their project.

    Now, due to the fact we have many different templates in different projects, it creates confusion and lack transparency in the selection
    Please help me solve this problem and fix this problem of maneging templates depends on different project?

Please sign in to leave a comment.