Project

General

Profile

Actions

Feature #20057

closed

Why Group can't be used as a Watcher in Issue?

Added by Rostislavs Kusnirenko almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Groups
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid

Description

Hi, is it correct, that "groups" functionality allows to define group(s), add members (users) to that group(s) - and after that, these new group(s) can be used:

  • group can be member of particular project (with particular role)
  • group can be used in reports
  • group can be defined as Assignee in issue

All mentioned functionality I get from changelogs (!!!) - as, if I correctly understand, Help is far-far from the current, latest Redmine release... (3.0.0+).

Anyway, if you can comment statements above - I will be happy to receive your clarification. However, my real question is following:

  • why it's not possible to use group as a Watcher? (in Issue)?

Thanks in advance,

Rostislav

Actions #1

Updated by Rostislavs Kusnirenko almost 10 years ago

Sorry, typo:

...and after that, these new group(s) can't be used...

Correct is:

...and after that, these new group(s) can be used...

Unfortunately, I can't edit ticket's definition, so, I wrote correction as comment..

Actions #2

Updated by Mischa The Evil almost 10 years ago

  • Description updated (diff)
  • Status changed from New to Closed
  • Resolution set to Invalid

I've modified the description according to the request.

Regarding your question: it actually belongs to the forum. We don't provide support using issues, they are designated for defect reports, feature requests and patches only.
Though, I think the answer is quite simple: AFAICT it has not been implemented and AFAIK it has not been requested yet.

Actions #3

Updated by Rostislavs Kusnirenko almost 10 years ago

Dear Evil The Mischa,

I am so, so sorry that I broke rules of your tracker.. Please, excuse me!

I willl try to proceed with my question on the mentioned forum.

Rostislav

Actions #4

Updated by Rostislav Kushnirenko almost 10 years ago

Dear Mischa The Evil, I have checked forum and think again on what you have said in your comment - then should I re-open my question as "Feature"? (Feature Request)? But you (Development Team) or community, will vote (if will vote :) ) for it - should it be included into roadmap or no. Correct?

And second. I have another, seems, not a question, but feature request - functionality "Category" (in "Issues") - why not to made it "shared" between Projects, e.g. configurable - some Category can be exclusive for particular Project, some - shared between many Projects. Should I create CR - or...?

Thanks in advance!!! And sorry, if I again wrote in incorrect place / incorrect "format" !!

Rostislav

Actions #5

Updated by Toshi MARUYAMA almost 10 years ago

Description request is duplicate of #4511.

Actions #6

Updated by Toshi MARUYAMA almost 10 years ago

Rostislav Kushnirenko wrote:

And second. I have another, seems, not a question, but feature request - functionality "Category" (in "Issues") - why not to made it "shared" between Projects, e.g. configurable - some Category can be exclusive for particular Project, some - shared between many Projects. Should I create CR - or...?

I think this is a part of #1853.

Actions

Also available in: Atom PDF