プロジェクト

全般

プロフィール

Vote #63079

完了

Disabling default ticket fields per tracker

Admin Redmine さんが3年以上前に追加. 3年以上前に更新.

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
開始日:
2008/04/23
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
47
issue_org_id:
1091
author_id:
876
assigned_to_id:
1
comments:
41
status_id:
5
tracker_id:
2
plus1:
20
affected_version:
closed_on:
affected_version_id:
ステータス-->[Closed]

説明

I want to create a tracker with all the custom fields. I don't want any default fields to be displayed in it


journals

Default fields can not be disabled for now.
--------------------------------------------------------------------------------
>Default fields can not be disabled for now

Are you going to provide the solution in the future?
--------------------------------------------------------------------------------
Fixed the issue-relationships...
--------------------------------------------------------------------------------
Mischa The Evil wrote:
> Fixed the issue-relationships...

Mischa, how about changing or adding to the title of this feature so that it describes the ones it duplicates also, more accurately.. ? I'm thinking a solution to this is more general than disabling the default ticket fields?
--------------------------------------------------------------------------------
Sorry, I see now that this is related to #703 and together these are enough. Feel free to remove/delete these non-productive comments :)
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1

I need to have a new issues interface that can be used by external parties. I don't want them to be able to see the "Assigned to" or "Due date" etc fields.

I am running 1.0.5 and I made the following changes to redmine/app/views/issues/_form.rhtml
-------------------------------------------------------------------------------
24,26c24,28
< <div id="attributes" class="attributes">
< <%= render :partial => 'issues/attributes' %>
< </div>
---
> <% if User.current.roles_for_project(@project).length != 1 || User.current.roles_for_project(@project)[0].name != "Reporter" %>
> <div id="attributes" class="attributes">
> <%= render :partial => 'issues/attributes' %>
> </div>
> <% end %>
-------------------------------------------------------------------------------

This will render the issue attributes IF AND ONLY IF the user is a "Reporter" role. This will also remove access to any custom fields.
It is a quick and VERY dirty hack but it is enough to keep me going until this issue is solved.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
This capability would be huge.
--------------------------------------------------------------------------------
I openeda feature request a time ago, which will include all this kind of field configuration.

See here Issue #8050
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
duplicate of #8050
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1 !!!!!!!!!!
--------------------------------------------------------------------------------
+1 Yes, indeed!

No reason not to include this feature. Arranging the form to your liking would also be quite useful. Right now, I added 4 extra fields and my eyes are already jumping around the form looking for the the ones I need to fill in and for those I want to skip.
--------------------------------------------------------------------------------
Feature added in r9912. You can now disable regular fields on the tracker form:

!standard_fields.png!
--------------------------------------------------------------------------------
That's required in issue #8417

> +1 Yes, indeed!
>
> No reason not to include this feature. Arranging the form to your liking would also be quite useful. Right now, I added 4 extra fields and my eyes are already jumping around the form looking for the the ones I need to fill in and for those I want to skip.

--------------------------------------------------------------------------------
IS this feature also will be enabled on the 1.4 world?
--------------------------------------------------------------------------------
joseph john wrote:
> IS this feature also will be enabled on the 1.4 world?

Sure not.
--------------------------------------------------------------------------------
Why do I still can't disable the "Status/Priority/File attaching/Watchers" field? People wanna add a complete new issue tracker things like meeting/billing/sales...
Badly need to need this feature!
--------------------------------------------------------------------------------
Wan Zhenhuan wrote:
> Why do I still can't disable the "Status/Priority/File attaching/Watchers" field? People wanna add a complete new issue tracker things like meeting/billing/sales...
> Badly need to need this feature!

Well, this could be solved after this patch is applied to the core #12005.

Best regards,
Daniel
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
But the "priority" field still seems permanent. Is there a way to include that in the list of default fields that can be disabled? I have a specific tracker that doesn't need this field and it's causing some mild confusion with issue reporters.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Is there a plugin to disable the Issue core fields such as assigned_to_id on a project level basis? As per the existing settings, only custom fields can be disabled on a per project basis. Standard fields can be disabled per tracker/role/user but not per project.

I want standard fields disable options same as custom fields in project settings also.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


related_issues

relates,Closed,703,Configurable required fields per tracker/status/role
relates,Closed,9700,Allow to configure the visibility of the fields of the “New issue” form per role
relates,Closed,12707,Typo in app/models/tracker.rb
relates,Closed,6637,"unwanted" features as plugins
duplicates,Closed,4434,Hide target version in ticket mask
duplicates,Closed,4387,Managing "description" field
duplicates,Closed,1296,Allow trackers to hide issue fields
duplicates,Closed,3737,Enabling to Remove Default Fields in New Project Creation
duplicates,Closed,3154,Remove default fields on new issue form
duplicates,Closed,5032,Ability to remove "Assigned to" field from particular tracker
duplicates,Closed,9736,custom field visibility based on tracker
duplicates,Closed,8150,Suggestion for editing Issue form
precedes,Closed,14584,Standard fields disabled for certain trackers still appear in email notifications

Admin Redmine さんが3年以上前に更新

  • カテゴリIssues_2 にセット
  • 対象バージョン2.1.0_47 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0