-
Suggestion
-
Resolution: Obsolete
-
None
-
None
-
None
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.
- has a derivative of
-
- Closed
- is cloned from
-
- Closed
- relates to
-
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
-
Page
Failed to load
-
Page Loading...
-
-
[JRASERVER-27613] Alternative JIRA Views
| Workflow | Original: JAC Suggestion Workflow [ 3063621 ] | New: JAC Suggestion Workflow 3 [ 3691798 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2604230 ] | New: JAC Suggestion Workflow [ 3063621 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2554416 ] | New: Confluence Workflow - Public Facing v4 [ 2604230 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342550 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2554416 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2111066 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342550 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2081200 ] | New: JIRA Bug Workflow w Kanban v6 [ 2111066 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 889335 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2081200 ] |
| Description |
Original:
*Background*
JIRA does not natively support the idea of field level security ( *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 Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-27613]. {panel} *Background* JIRA does not natively support the idea of field level security ( *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. |
| Link |
New:
This issue relates to |
I need this desperately! I don't think all users need to see time tracking.