プロジェクト

全般

プロフィール

Vote #66963

未完了

Subcategories or multiple category tags or multi-select custom fields

Admin Redmine さんがほぼ4年前に追加. ほぼ4年前に更新.

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

0%

予定工数:
category_id:
2
version_id:
0
issue_org_id:
5220
author_id:
13508
assigned_to_id:
0
comments:
9
status_id:
1
tracker_id:
2
plus1:
6
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

Let me start out by saying that I'm quite impressed with Redmine and how far it's come.

I'll likely look to implement this but there are a couple features that seem to be either missing or not quite 100%. The biggest one that I think I'll need more than any other (that is outstanding) is:

I'd like to be able to have subcategories or some way of organizing a simple hierarchy within a project. For example, I open a new issue in project A. It involves an issue with project A's web interface. I can categorize that use Category perfectly now. But I'd like to be able to assign a subcategory of 'Admin Screen' along with the category 'Web Interface'. Possible implementations:

  1. Create subproject 'Web Interface' to parent project 'A'. I can do this now and it would work but I'd need to be able to be viewing the project 'A' and when I create a new issue, I'd need to be able to create it from project 'A' but for subproject 'Web Interface'. I really don't like this approach even if I could do this.

  2. Sub-Category field. This would be perfect but isn't available in trunk (or 0.9.x as far as I know). There is a patch out there but hasn't been touched in a while and has fallen out of sync with code. The only other thing with this though to mention is obviously it's only two level (category->subcategories)

  3. Allow selection of multiple category fields. So 'Web Interface' and 'Admin Screen' would be categories and I could chose/tag BOTH of those as categories for the issue. This ok for reporting and whatnot and would satisfy my need I guess.

  4. Allow multiple selection of custom fields to basically create a custom field to replace the category field and implement the same as number 3 above.

I may be missing other ideas but from what I've come up with from searching and whatnot, this seems to be it.

Am I missing any new developments or ideas? I'm sort of surprised this feature/function is still outstanding and would love to see a direction taken. I'm willing to participate and help move this forward with the help of others.

Can we resume the discussion and get this feature banged out?

Thanks.


journals

Moving issue categories to be tags/labels would be great. I've been wanting to tag things as 'javascript' and 'ajax', or as 'javascript' and 'filters', for instance.
--------------------------------------------------------------------------------
+1

This would be huge for us.
--------------------------------------------------------------------------------
+1
This also help us a lot!
--------------------------------------------------------------------------------
great help if apply
--------------------------------------------------------------------------------
+1. This would come in handy as long as existing values and to a lesser extent custom queries aren't adversely affected.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
+1 on subcategories.
--------------------------------------------------------------------------------


related_issues

relates,Closed,1189,Multiselect custom fields
relates,New,3718,Sevaral categories for an issue
relates,New,3966,Tickets Subcategories
relates,New,15387,Hierarchical categories (nestable)
duplicates,Closed,7761,Add ability to add multiple Assignees and categories to some Issue

Admin Redmine さんがほぼ4年前に更新

  • カテゴリIssues_2 にセット

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

いいね!0
いいね!0