[IM] query-question: how to filtering for siproject-fields?

[JensN.]

Hi @all,

it seems that i cannot use siproject-fields in the query-builder. Is there any other way to filter over such fields?

thanks, Jens

[KaelLizak]

Hello Jens,

What kind of query, exactly, are you trying to build?

Regards,
Kael

[JensN.]

Hi Kael,

we want to see two things:

1. is an item in integrity connected to a checkpoint in source via siproject (we know changepackages, but thats not what we want) or not.

2. if an item is connected, than we want to know the exact entry in this siproject-field.

Both isnt possible with queries (or any other ootb-functionality) or not?

regards, Jens

[mrump]

Hi Jens,

I totally agree that there is something missing in the PTC query framework when it comes to source .

Nevertheless, there might be a workaround using Computed Expressions:

At least in Reports I verified that you can use something like this:

Length("SI Project") > 0?true:false

to identify issues that have any SI project link.

OR

Locate(text("myProjectName"), "SI Project") > 0?true:false

to identify issues that have a SI project link to a specific project.

I am quite sure you can use these as dynamically computated fields in your item setup as well.

Than it should be possible to query these fields.

HTH

Matthias

[JensN.]

Hi Matthias,

again you saved my day

cheers, Jens

[KaelLizak]

Hello Jens,

we want to see two things:

1. is an item in integrity connected to a checkpoint in source via siproject (we know changepackages, but thats not what we want) or not.

2. if an item is connected, than we want to know the exact entry in this siproject-field.

Both isnt possible with queries (or any other ootb-functionality) or not?

regards, Jens

Right now I don't think 1. is possible. Please contact Integrity Support if you haven't already done so to open a case. I suspect it will be filed as a feature request, but somebody might be able to figure this out.

I think 2 might be possible, but I don't know the functionality well enough to be able to come up with something quickly there.

The two items will likely be split into two separate tickets.

Regards,

Kael

[tketz]

Hello Jens,

i totally agree with you and Matthias too, that here is something missing.

We have another work around with a Trigger.

When we use a SI project field, we also have fields like "SourceProject" and "Checkpoint". These fields are not editable and filled from a trigger, every time the SI Project Field was changed.

Hope that helps.