• Icon: Suggestion Suggestion
    • Resolution: Obsolete
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Background
      JIRA does not natively support the idea of field level security (JRA-1330), the most popular of which is the ability to the hide Time Tracking fields from customers (JRA-2364). We know that a lot of customers really want a way for JIRA to solve this kind of problem.

      View Ports
      Internally at Atlassian we have been throwing around the idea of what we call "View Ports". The idea behind this is that admins can configure an alternative view of the JIRA View Issue screen for different groups. One of the items that can be configured is the ability to choose what fields are shown in the View Port.

      Example Scenario
      You have a company that specialises in custom development solutions and have 10 internal staff members with 200 external customers. You want to manage all your issues in one JIRA project but you do not want to expose the time tracking fields to your customers.

      View Port Solution
      1. Admin creates a JIRA group for all the 'external customers'.
      2. Admin then creates a View Port for this group only.
      3. Admin configures the View Port to show all fields except time tracking.

      When anyone in the 'external customers' group logs into a specific url, they are taken to this View Port. They will not be able to login into the normal JIRA system.

      Comments Please
      We'd love to get your feedback in this solution and if it would work for your company.

            [JRASERVER-27613] Alternative JIRA Views

            I need this desperately! I don't think all users need to see time tracking.

            Joris Weimar added a comment - I need this desperately! I don't think all users need to see time tracking.

            Today another user asked for this feature. They want to use JIRA but want different teams to see different fields.
            Just for you to know.

            Emre Toptancı [OBSS] added a comment - Today another user asked for this feature. They want to use JIRA but want different teams to see different fields. Just for you to know.

            @Atlassian
            No matter what we use JIRA for, there are almost always two parties involved. Service provider and service consumer (or customer). When there is more than one party, there will always be some information that needs to be hid from customer. Service Desk is a solution that solves only a small portion of this problem. The need to hide some fields from some users in the conventional JIRA interface is critical.

            The initial idea of viewports was a promising one yet you decided not to implement it. Believe me guys, Service Desk can not meet those needs. You say it is very hard to implement this feature since it would require large portions of JIRA to be rewritten. You know what: You should start immediately!!!

            JIRA is moving to an upper league these days. We, as a partner, are positioning JIRA for all kinds of needs: Request management, project & portfolio management, service desk, audits, etc... you name it. Believe me when I say this feature is needed desparately. This is more important than Service Desk or Portfolio. There is no version of future that JIRA can go on without this feature forever. Sooner or later you will have to implement this. The sooner it is done the less damage. (We are currently implementing a very large scale Atlassian project and we suffered a lot because of this. I can not put enough emphasis on how important this is.)

            Emre Toptancı [OBSS] added a comment - @Atlassian No matter what we use JIRA for, there are almost always two parties involved. Service provider and service consumer (or customer). When there is more than one party, there will always be some information that needs to be hid from customer. Service Desk is a solution that solves only a small portion of this problem. The need to hide some fields from some users in the conventional JIRA interface is critical. The initial idea of viewports was a promising one yet you decided not to implement it. Believe me guys, Service Desk can not meet those needs. You say it is very hard to implement this feature since it would require large portions of JIRA to be rewritten. You know what: You should start immediately!!! JIRA is moving to an upper league these days. We, as a partner, are positioning JIRA for all kinds of needs: Request management, project & portfolio management, service desk, audits, etc... you name it. Believe me when I say this feature is needed desparately. This is more important than Service Desk or Portfolio. There is no version of future that JIRA can go on without this feature forever. Sooner or later you will have to implement this. The sooner it is done the less damage. (We are currently implementing a very large scale Atlassian project and we suffered a lot because of this. I can not put enough emphasis on how important this is.)

            Gebsun added a comment -

            Hello guys,

            The mentioned Hide Time Tracking plugin is now a mature product and time tracking information is not visible in JIRA UI (for users without 'work on issues' permission).
            In case of any problems you can raise an issue at https://gebsun.atlassian.net/browse/HTT

            Regards,
            Gebsun

            Gebsun added a comment - Hello guys, The mentioned Hide Time Tracking plugin is now a mature product and time tracking information is not visible in JIRA UI (for users without 'work on issues' permission). In case of any problems you can raise an issue at https://gebsun.atlassian.net/browse/HTT Regards, Gebsun

            Gandalf added a comment -

            @Alexander: Many thanks for the info. It's indeed possible that this plugin is still early stage and that it does not yet cover all aspects.
            In fact, this type of plugin was expected to be developed by Atlassian (Jira) in order to provide a solution for "hiding time tracking fields". It's a pity this has to be performed by a third party.

            Gandalf added a comment - @Alexander: Many thanks for the info. It's indeed possible that this plugin is still early stage and that it does not yet cover all aspects. In fact, this type of plugin was expected to be developed by Atlassian (Jira) in order to provide a solution for "hiding time tracking fields". It's a pity this has to be performed by a third party.

            @Jean-Jacques I would advise you against using this new plugin at all in its current state. It just seems to work, but actually everything is still visible in change history, activity streams etc etc.

            Alex Shchagin added a comment - @Jean-Jacques I would advise you against using this new plugin at all in its current state. It just seems to work, but actually everything is still visible in change history, activity streams etc etc.

            Gandalf added a comment -

            @Ronald, we're indeed in the same boat and facing exactly the same situation.
            Let's hope that Atlassian (Jira) will surprise us by quickly enabling this long awaited plugin. Just want to stay positive after all.

            Gandalf added a comment - @Ronald, we're indeed in the same boat and facing exactly the same situation. Let's hope that Atlassian (Jira) will surprise us by quickly enabling this long awaited plugin. Just want to stay positive after all.

            We're in the same boat. There's a lot of things we like about Jira and we haven't found a replacement.
            The need to hide time tracking doesn't affect all our projects so for the moment we're putting up with the missing functionality.

            Ronald Vallenduuk added a comment - We're in the same boat. There's a lot of things we like about Jira and we haven't found a replacement. The need to hide time tracking doesn't affect all our projects so for the moment we're putting up with the missing functionality.

            Gandalf added a comment -

            @Ronald Vallenduuk...thanks for your reply.
            You indeed pointed out the different options and we looked/tried all of them.
            Leaving Jira behind is indeed an option, all the others are not. But I must also say, on a positive note, we've a lot of satisfaction with other Jira features and Jira in general with Confluence, Bit Bucket and so on. But this "hide time tracking fields" is indeed the cause of lots of frustration on our side. Did you find another solution?

            Gandalf added a comment - @Ronald Vallenduuk...thanks for your reply. You indeed pointed out the different options and we looked/tried all of them. Leaving Jira behind is indeed an option, all the others are not. But I must also say, on a positive note, we've a lot of satisfaction with other Jira features and Jira in general with Confluence, Bit Bucket and so on. But this "hide time tracking fields" is indeed the cause of lots of frustration on our side. Did you find another solution?

            @Jean-Jacques Courtens: Thank you. I will check out the plugin. Hope it will fit our needs.

            Tobias Schenke [commsult AG] added a comment - @Jean-Jacques Courtens: Thank you. I will check out the plugin. Hope it will fit our needs.

              Unassigned Unassigned
              shamid@atlassian.com shihab
              Votes:
              194 Vote for this issue
              Watchers:
              197 Start watching this issue

                Created:
                Updated:
                Resolved: