Filter in confluence

karthik A Dec 15, 2013

Hi friends,

I added the "Filter result" Macro in the page, but during edit the page it display the error.

Please refer the attachment.

How can i solve the issue. please share your thoughts,

Thanks in advance,

Karthik A.

3 answers

0 vote

Nic Brough [Adaptavist] Community Champion Dec 15, 2013

The message you are getting is telling you what is wrong. The filter you are choosing has errors that you need to fix, specifically that the project you've selected in the filter does not exist and that the field "due" is not included.

In both cases, it could be because the current user cannot "browse" the project, and that's what you should check first.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 vote

karthik A Dec 15, 2013

Hi Nic,

Thanks for your updates, The current user has browse permission on the project but the 2nd screen shot 2nd point (Field 'due' does not exist or this field cannot be viewed by anonymous users..) issues occurs again.

Thanks,

Karthik A.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Nic Brough [Adaptavist] Community Champion Dec 15, 2013

Ok, so when you log into Jira as that user and look at an issue? Do they see the "due" field?

A couple of other minor points - I'm sort of assuming by "due", you mean "the due date", the system field? Also, you aren't using any plugins like behaviours, field security or something else that obscures fields, and you haven't been trying to do things with javascript?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Mads Nicolai Dec 16, 2013

I am experiencing the same problem, with filters that have no issues when used in JIRA's issue search and the filter result dashboard gadget.

The filter result macro in confluence was working without any issues last week, but monday morning they started to report the same problems as seen in karthik A's second screenshot.

I can see in the upgrade history that there was an updgrade at 16/Dec/13 8:00 CET (Monday morning), about the same time this filter result issue started.

Can the upgrade have cuased this issue?

/Mads