• Type: Bug
• Resolution: Won't Fix
• Priority: Medium
• Component/s: Administration - Fields, Issue Types, Screens, Schemes and Priorities
• Labels:

  • affects-cloud
  • affects-server
  • jira-ninjas-explore
  • jira-run
  • jsw-s2
  • no-cvss-required
  • st10

[JRACLOUD-37117] Grant "Browse Project" permission to "User Custom Field Value" makes project visible to all users

Gerson Gutierrez made changes - 10/Nov/2023 9:38 AM

Labels

Original: affects-cloud affects-server jira-ninjas-explore jira-run no-cvss-required st10

New: affects-cloud affects-server jira-ninjas-explore jira-run jsw-s2 no-cvss-required st10

Michal Keshet made changes - 31/Aug/2020 6:05 AM

Link

New: This issue was cloned as JRACLOUD-75053 [ JRACLOUD-75053 ]

Monique Khairuliana (Inactive) made changes - 15/Aug/2019 5:42 AM

Workflow	Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1869406 ]	New: JAC Bug Workflow v3 [ 3361417 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Carlos Ughini made changes - 06/Dec/2018 9:45 PM

Description

Original: {panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRASERVER-37117]. {panel}   {panel:title=Status Update|borderStyle=solid|borderColor=#ff7f7f|titleBGColor=#ff7f7f|bgColor=#e5e5e5} Hi everyone, We have reviewed the status of this issue and there are not currently plans to fix this bug in *Jira Cloud*. Extensive analysis over the last couple years has indicated that the complexity of addressing this bug without causing performance degradation for customers using permission schemes with user custom field grants is significant. Based on the number of customers that have actually been affected, we cannot justify the effort required to address it at this time. Thanks for your understanding. Regards, Dave Meyer Senior Product Manager, Jira Cloud {panel}    If in your permission schema, you grant _Browse Project_ permission to _"User Custom Field Value"_, the project is visible to all users. Regardless of whether that field is filled or not.  JRA-31720 fixed that for the current assignee - i had hoped this would work for custom fields too.

New: {panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRASERVER-37117]. {panel}     {panel:title=Status Update|borderStyle=solid|borderColor=#ff7f7f|titleBGColor=#ff7f7f|bgColor=#e5e5e5} Hi everyone, We have reviewed the status of this issue and there are not currently plans to fix this bug in *Jira Cloud*. Extensive analysis over the last couple years has indicated that the complexity of addressing this bug without causing performance degradation for customers using permission schemes with user custom field grants is significant. Based on the number of customers that have actually been affected, we cannot justify the effort required to address it at this time. Thanks for your understanding. Regards, Dave Meyer Senior Product Manager, Jira Cloud {panel}       If in your permission schema, you grant _Browse Project_ permission to _"User Custom Field Value"_, the project is visible to all users. Regardless of whether that field is filled or not.  JRA-31720 fixed that for the current assignee - i had hoped this would work for custom fields too.

Eric S (Inactive) made changes - 19/Sep/2018 4:57 AM

Component/s		New: Project Administration - Issue type, fields and Other [ 53196 ]
Component/s	Original: Project Administration [ 46539 ]

Dave Meyer made changes - 24/Apr/2018 7:14 AM

Resolution		New: Won't Fix [ 2 ]
Status	Original: Verified [ 10005 ]	New: Resolved [ 5 ]

Dave Meyer made changes - 24/Apr/2018 7:14 AM

Status

Original: Open [ 1 ]

New: Verified [ 10005 ]

Dario B made changes - 13/Apr/2018 2:44 PM

Status

Original: Awaiting Development [ 10038 ]

New: Open [ 1 ]

Dario B made changes - 13/Apr/2018 2:44 PM

Description

Original: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRASERVER-37117].   {panel} If in your permission schema, you grant _Browse Project_ permission to _"User Custom Field Value"_, the project is visible to all users. Regardless of whether that field is filled or not. JRA-31720 fixed that for the current assignee - i had hoped this would work for custom fields too.

New: {panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRASERVER-37117]. {panel}   {panel:title=Status Update|borderStyle=solid|borderColor=#ff7f7f|titleBGColor=#ff7f7f|bgColor=#e5e5e5} Hi everyone, We have reviewed the status of this issue and there are not currently plans to fix this bug in *Jira Cloud*. Extensive analysis over the last couple years has indicated that the complexity of addressing this bug without causing performance degradation for customers using permission schemes with user custom field grants is significant. Based on the number of customers that have actually been affected, we cannot justify the effort required to address it at this time. Thanks for your understanding. Regards, Dave Meyer Senior Product Manager, Jira Cloud {panel}    If in your permission schema, you grant _Browse Project_ permission to _"User Custom Field Value"_, the project is visible to all users. Regardless of whether that field is filled or not.  JRA-31720 fixed that for the current assignee - i had hoped this would work for custom fields too.

SET Analytics Bot made changes - 05/Apr/2018 12:13 AM

Support reference count

Original: 17

New: 18

Load more older history items