'Filter or project': provide a way of distinguishing between both

[Ignacio Pulgar Martín]

Hi Andriy,

On https://<mine>.atlassian.net/plugins/servlet/ac/timereports/timereports the 'Filter or project' field doesn't make it possible to differentiate if the suggested name refers to a project or to a filter.

I'd suggest using separated fields for both things.

Besides, selecting simultaneously filters and projects on the same report seems to retrieve less values than it should:

It would be expectable that if I have a project selected, and add a filter to it, then I should only have more issues, or equal number of issues, and never less.

Not tested enough in order to ascertain whether filters act as an additional condition (restricting shown values), instead of an OR.

Have noticed this behaviour on a couple of users here, but have not being testing myself with all the possibilities.

[Andriy Zhdanov]

Hi Ignacio,

I agree it's a bit confusing, but I thought it's JIRA standard-like approach since they provide special REST api of this kind. But I will see if it can be improved.

As for the Option itself, it builds condition like this: (project1 or project2) and (filter1 or filter2). Hope it's quite intuitively useful. Otherwise I'm open for suggestions.

Thank you.

[Ignacio Pulgar Martín]

IMHO, it is counterintuitive adding values to a field that give more or less results depending on what you include there... unless the values are being shown on an editable JQL sentence.

Besides of that, consider that filter names can be exactly the same than project names.

Another issue I've found is that too long filter/project names can't be viewed before having made a selection and look at the tag that is being included on the top-right side.

As there are many filters and projects starting with the same sequence of characters, you cannot see what ar you selecting exactly:

I think the suggested tooltip would be really helpful prefixing with filter: or project: , depending on the value.

Mind that selecting project A and adding a filter X with this JQL: "project = B and status != Closed" will retrieve 0 results.

This is not what end users expect to happen when adding more values there.

Best regards!

[Andriy Zhdanov]

Thank you, good points!

[Ignacio Pulgar Martín]

Can a JQL field be added to be used directly without having to save a filter?

[Andriy Zhdanov]

Not now, may be later it will be possible to have similar to Issue Navigator query builder.

[Ignacio Pulgar Martín]

Not a problem, I will save a JQL filter named "_temp_JQL" and save&update my search that way.

Thanks!

[Andriy Zhdanov]

Hi Ignacio,

It should be fixed now.

Note, I'll keep issue#775 for possible further improvements of this control, including support for custom jql.

Thank you.

[Ignacio Pulgar Martín]

Great news!! :) Will check it tomorrow! Thanks!

[Ignacio Pulgar Martín]

Cool! Really useful!

Have you discarded adding the prefix 'filter: ' or 'project: ' in the tooltip?

Anyway, this is a great advancement :)

Thanks!

[Andriy Zhdanov]

Great, glad you like it.

I think it's better not to add Filter: or Project: in names and tooltips, not to consume extra characters, and it should be quite clear what are you looking at, since there are two sections.

[Ignacio Pulgar Martín]

That's right!! Cooler!!!

Didn't notice on a quick review!

Super-thanks!

[Ignacio Pulgar Martín]

Hi @azhdanov,

The tooltip is only being shown for the first filter suggested in the 'Filter or Project' field.

[Andriy Zhdanov]

Hi Ignacio,

It's shown for all long names only, more than 25 characters. May be other filters are not that long, and still do not fit into the shown area?

Thank you.