Modify

Opened 2 years ago

Last modified 14 months ago

#11572 new enhancement

Only show valid milestones/components in query form

Reported by: endquote Owned by: falkb
Priority: normal Component: SimpleMultiProjectPlugin
Severity: normal Keywords:
Cc: Trac Release: 1.0

Description

In the custom query form, if you set a "milestone is" query, that dropdown has every milestone from every project. I wish it only showed open projects. Even better, if the query is filtering on a project, it should only show milestones for that project.

Attachments (0)

Change History (8)

comment:1 Changed 2 years ago by endquote

  • Summary changed from Only show valid milestones in query form to Only show valid milestones/components in query form

The components list has the same problem.

Other filters, such as priority, etc, would as well. However at least for me, those are the same for every project.

comment:2 in reply to: ↑ description Changed 2 years ago by falkb

Replying to endquote:

In the custom query form, if you set a "milestone is" query, that dropdown has every milestone from every project.

Yes, that's a weakness of this plugin that it has no implementation regarding the query system. I need to find out first where I can hook into things there to filter the lists with the project conditions.

comment:3 Changed 19 months ago by Cinc

Just to throw in my 2 cents.

If you filtered any of the drop down lists by open projects it would be impossible/difficult to search for old tickets belonging to projects already closed. Not sure if it's wise to hide stuff from the general query page.

OTOH filtering the e.g. milestone list by an already selected project may be useful but difficult. The order in which you select milestone/project/version would sometimes hide information sometimes not probably confusing the user greatly.

comment:4 follow-ups: Changed 17 months ago by nenad@…

I think that first step towards general implementation on "show milestones only from within selected project" has to be query results limiting based on projects user has access to. For example, even though user is limited to one project, using some of the "View tickets" queries one can see tickets (or at least summaries) related to the projects he has no access to.

Partial workaround is to use PrivateTicketsPlugin, but even with this plugin milestone titles are show.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 17 months ago by nenad@…

Replying to nenad@…:

Partial workaround is to use PrivateTicketsPlugin, but even with this plugin milestone titles are show.

The other part of workaround is to disable REPORT_VIEW and enable ROADMAP_VIEW + MILESTONE_VIEW.

comment:6 in reply to: ↑ 5 Changed 17 months ago by nenad@…

Replying to nenad@…:

Replying to nenad@…:

Partial workaround is to use PrivateTicketsPlugin, but even with this plugin milestone titles are show.

The other part of workaround is to disable REPORT_VIEW and enable ROADMAP_VIEW + MILESTONE_VIEW.

Well, this works only partially - once Milestones from the project are shown and users selects link to query, query with all milestones from all projects appears again.

In other words, it is not possible to get list of tickets in projects user has access to, without breaking basic separation between projects.

comment:7 in reply to: ↑ 4 ; follow-up: Changed 14 months ago by Cinc-th

Replying to nenad@…:

I think that first step towards general implementation on "show milestones only from within selected project" has to be query results limiting based on projects user has access to. For example, even though user is limited to one project, using some of the "View tickets" queries one can see tickets (or at least summaries) related to the projects he has no access to.

Is my understanding correct to let the user select even 'forbidden' milestones and projects but hide the results?

comment:8 in reply to: ↑ 7 Changed 14 months ago by nenad@…

Replying to Cinc-th:

Replying to nenad@…:

I think that first step towards general implementation on "show milestones only from within selected project" has to be query results limiting based on projects user has access to. For example, even though user is limited to one project, using some of the "View tickets" queries one can see tickets (or at least summaries) related to the projects he has no access to.

Is my understanding correct to let the user select even 'forbidden' milestones and projects but hide the results?

No, user should not be able to see anything from the project he has no access to.

Add Comment

Modify Ticket

Action
as new The owner will remain falkb.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.