Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-27613

Alternative JIRA Views

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Obsolete
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.

            [JRACLOUD-27613] Alternative JIRA Views

            Charles Trilha (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-27613].
              {panel}

            *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.             		New: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-27613].
            {panel}
            *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.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3140799 ] New: JAC Suggestion Workflow 3 [ 3633700 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2328738 ] New: JAC Suggestion Workflow [ 3140799 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2098414 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2328738 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2060043 ] New: JIRA Bug Workflow w Kanban v6 [ 2098414 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 1865957 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2060043 ]
            jonah (Inactive) made changes -
            Description Original: *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.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-27613].
              {panel}

            *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.
            jonah (Inactive) made changes -
            Link New: This issue is related to JRASERVER-27613 [ JRASERVER-27613 ]
            vkharisma made changes -
            Link New: This issue has a derivative of JSDCLOUD-201 [ JSDCLOUD-201 ]
            vkharisma made changes -
            Project Import New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ]

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

                Created:
                Updated:
                Resolved: