Remove the Everyone share option from filters in Jira server
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
Prior to Jira 7.2.2, JIRA Administrators do not wish to allow filters to be shared with 'Everyone', as it makes them visible to anonymous (unauthenticated) users. This is due to the fact that you can't disable anonymous access to general pages in JIRA globally.
This behaviour is changed after the implementation of JRA-23255 - Getting issue details... STATUS whereby JIRA administrators can now disable the ability to share dashboards and filters publicly (anonymous users) via a new global setting "Public sharing". Please read the description of the Suggestion ticket for more information on this change.
This article is a collection of workarounds that you can use to exclude the sharing of filters with anonymous users in Jira versions prior to 7.2.2. Some of these methods may still work in versions greater than 7.2.2 so you can continue using them, though we recommend just disabling the Public sharing (or equivalent) permission of your Jira application instead.
There are two possible solutions. They can be used individually or together if both outcomes are required:
a) You can remove the option from the drop-down select list so it is not possible to share with 'Everyone'.
With this solution the options left for sharing a filter are with a group or project role that the user is member of. See more details on Sharing a Filter.
b) You can restrict access to the page URL for managing filters to only allow authenticated users access.
If a anonymous user attempts to access the page they will be re-directed to the login page.
You may also be interested on this related article:
- How to bulk restrict Filters and Dashboards shared with anyone on the web or logged-in users in Jira
ソリューション
The alternatives presented here are considered customizations and are unsupported by Atlassian — only presented AS-IS for Admins to evaluate, assess the tradeoffs and implement at their own risk.
You may learn more of the tradeoffs and caveats of such customizations in How to customize Jira with JavaScript and CSS.
本ページの内容には、Atlassian ソフトウェアのカスタマイズや拡張 (CSS ルール、HTML、JavaScript の追加/変更など) を行う手順が含まれています。アトラシアン サポートの提供 の通り、Atlassia 製品に加えられたカスタマイズはサポートされません。この資料は情報提供のみを目的として提供されています。内容はお客様自身の責任でご利用ください。
本件またはカスタマイズに関するご質問は、コミュニティの Atlassian Answers で質問してください。または、アトラシアン ソリューション パートナー にご相談いただくことをご検討ください。