Mailing List Archive

1 2 3  View All
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
On May 15, 2006, at 7:31 AM, Cyriaque Dupoirieux wrote:
> le 15/05/2006 16:17 Web Maestro Clay a écrit :
>> On May 14, 2006, at 4:33 AM, jira@apache.org wrote:
>>> Issue Subscription
>>> Filter: FOR-open-with-patch (7 issues)
>>> Subscriber: rgardler
>>>
>>> Key Summary
>>> FOR-368 Add ihtml to "Deprecation of .ehtml and .ihtml"
>>> reference
>>> http://issues.apache.org/jira/browse/FOR-368
>>
>> FOR-368 was a minor bug in the 0.6 documentation. The reference no
>> longer exists, and IMO, this bug can be closed.
> +1,
> I already point this in the last comment of this FOR (26th of
> April) But no one answered me :-( .
>
> WDOT ?
>
> Cyriaque,

I thought I answered. ;-)

Web Maestro Clay
the.webmaestro@gmail.com

My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (7 issues)
Subscriber: rgardler


Key Summary
FOR-885 Mistyped fragment in website link
http://issues.apache.org/jira/browse/FOR-885
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (7 issues)
Subscriber: rgardler


Key Summary
FOR-885 Mistyped fragment in website link
http://issues.apache.org/jira/browse/FOR-885
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
El lun, 29-05-2006 a las 14:13 +0100, jira@apache.org escribió:
> FOR-525 Making views XHTML compliant
> http://issues.apache.org/jira/browse/FOR-525

Status: Resolved

Hi all,

can we modify the FOR-open-with-patch that resolved issue does not
appear anymore?

salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (12 issues)
Subscriber: rgardler


Key Summary
FOR-824 HowTo DTD 2.0 <a> elements not transformed correctly
http://issues.apache.org/jira/browse/FOR-824
FOR-814 Add documentation to explain how to aggregate data
http://issues.apache.org/jira/browse/FOR-814
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-525 Making views XHTML compliant
http://issues.apache.org/jira/browse/FOR-525
FOR-518 Change toolbox font in skinconf.xml for pelt
http://issues.apache.org/jira/browse/FOR-518
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-368 Add ihtml to "Deprecation of .ehtml and .ihtml" reference
http://issues.apache.org/jira/browse/FOR-368
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280
FOR-275 front-piece title page for pdf-output
http://issues.apache.org/jira/browse/FOR-275
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
Thorsten Scherler wrote:
> El lun, 29-05-2006 a las 14:13 +0100, jira@apache.org escribió:
>
>>FOR-525 Making views XHTML compliant
>> http://issues.apache.org/jira/browse/FOR-525
>
>
> Status: Resolved
>
> Hi all,
>
> can we modify the FOR-open-with-patch that resolved issue does not
> appear anymore?

Resolved is not closed. This filter is for open issues with a patch,
hence a resolved issues appears. To stop it appearing the issue needs to
be closed.

Of course, that begs the question "what is the difference between
resolved and closed?"

Ross
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
El lun, 29-05-2006 a las 20:38 +0100, Ross Gardler escribió:
> Thorsten Scherler wrote:
> > El lun, 29-05-2006 a las 14:13 +0100, jira@apache.org escribió:
> >
> >>FOR-525 Making views XHTML compliant
> >> http://issues.apache.org/jira/browse/FOR-525
> >
> >
> > Status: Resolved
> >
> > Hi all,
> >
> > can we modify the FOR-open-with-patch that resolved issue does not
> > appear anymore?
>
> Resolved is not closed. This filter is for open issues with a patch,
> hence a resolved issues appears. To stop it appearing the issue needs to
> be closed.
>
> Of course, that begs the question "what is the difference between
> resolved and closed?"

Yeah, I normally resolve issues and not close them because of
search-ability.

This leads further to the question should we better close issues instead
of resolving it?

Would this help that people do not reuse issues?

Maybe we should just adjust the filter and treat resolved issue as "not
open" issues. That definitely will reduce my flashbacks.

salu2
--
thorsten

"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
On May 29, 2006, at 4:31 PM, Thorsten Scherler wrote:
> This leads further to the question should we better close issues
> instead
> of resolving it?

I was bitten by this one... Since it wasn't 'closed' but instead was
'resolved' I figured (incorrectly!) it was open for more... Lesson
learned! No harm no foul!

> Would this help that people do not reuse issues?
>
> Maybe we should just adjust the filter and treat resolved issue as
> "not
> open" issues. That definitely will reduce my flashbacks.
>
> salu2
> --
> thorsten

Web Maestro Clay
the.webmaestro@gmail.com

My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
Thorsten Scherler wrote:
> Ross Gardler escribi??:
> > Thorsten Scherler wrote:
> > >
> > > can we modify the FOR-open-with-patch that resolved issue does not
> > > appear anymore?
> >
> > Resolved is not closed. This filter is for open issues with a patch,
> > hence a resolved issues appears. To stop it appearing the issue needs to
> > be closed.
> >
> > Of course, that begs the question "what is the difference between
> > resolved and closed?"
>
> Yeah, I normally resolve issues and not close them because of
> search-ability.

I always close issues with Resolution=Fixed.
For issues that have only a workaround, i have
marked as Incomplete and left them open because
they are not yet finished.

Why do you leave them open? Wouldn't that just make
searching worse?

> This leads further to the question should we better close issues instead
> of resolving it?

Both.

I just hit the Close button and it shows a Resolution option.
It sounds like you might be doing it in two steps:
Resolve then CLose.

> Would this help that people do not reuse issues?

Yes.

> Maybe we should just adjust the filter and treat resolved issue as "not
> open" issues. That definitely will reduce my flashbacks.

Better that you close issues.

-David
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
El lun, 29-05-2006 a las 16:41 -0700, Web Maestro Clay escribió:
> On May 29, 2006, at 4:31 PM, Thorsten Scherler wrote:
> > This leads further to the question should we better close issues
> > instead
> > of resolving it?
>
> I was bitten by this one...

doh

no, please.

> Since it wasn't 'closed' but instead was
> 'resolved' I figured (incorrectly!) it was open for more...

David just clearly stated that you have been right.

> Lesson
> learned!

We are still learning the lesson.

> No harm no foul!

I just trying to figure out the right approach.

salu2
--
thorsten

"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
El mar, 30-05-2006 a las 09:47 +1000, David Crossley escribió:
> Thorsten Scherler wrote:
> > Ross Gardler escribi??:
> > > Thorsten Scherler wrote:
> > > >
> > > > can we modify the FOR-open-with-patch that resolved issue does not
> > > > appear anymore?
> > >
> > > Resolved is not closed. This filter is for open issues with a patch,
> > > hence a resolved issues appears. To stop it appearing the issue needs to
> > > be closed.
> > >
> > > Of course, that begs the question "what is the difference between
> > > resolved and closed?"
> >
> > Yeah, I normally resolve issues and not close them because of
> > search-ability.
>
> I always close issues with Resolution=Fixed.
> For issues that have only a workaround, i have
> marked as Incomplete and left them open because
> they are not yet finished.
>
> Why do you leave them open?
> Wouldn't that just make
> searching worse?

I cannot recall the thread where I learned that marking issues as
resolved and not close them is sometimes very useful.

For example FOR-828. I resolved this issue and not closed it since I see
it as reference. It is an example how to fix a specific problem rather
then a bug. Next time I am looking for information on IE failing to read
the UTF-8 character encoding I will turn to this issue. Similar are the
documentation issues.

>
> > This leads further to the question should we better close issues instead
> > of resolving it?
>
> Both.
>
> I just hit the Close button and it shows a Resolution option.
> It sounds like you might be doing it in two steps:
> Resolve then CLose.
>
> > Would this help that people do not reuse issues?
>
> Yes.
>
> > Maybe we should just adjust the filter and treat resolved issue as "not
> > open" issues. That definitely will reduce my flashbacks.
>
> Better that you close issues.
>

ok, will do so in the future.

salu2
--
thorsten

"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
Thorsten Scherler wrote:
> David Crossley escribi??:
> > Thorsten Scherler wrote:
> > > Ross Gardler escribi??:
> > > > Thorsten Scherler wrote:
> > > > >
> > > > > can we modify the FOR-open-with-patch that resolved issue does not
> > > > > appear anymore?
> > > >
> > > > Resolved is not closed. This filter is for open issues with a patch,
> > > > hence a resolved issues appears. To stop it appearing the issue needs to
> > > > be closed.
> > > >
> > > > Of course, that begs the question "what is the difference between
> > > > resolved and closed?"
> > >
> > > Yeah, I normally resolve issues and not close them because of
> > > search-ability.
> >
> > I always close issues with Resolution=Fixed.
> > For issues that have only a workaround, i have
> > marked as Incomplete and left them open because
> > they are not yet finished.
> >
> > Why do you leave them open?
> > Wouldn't that just make
> > searching worse?
>
> I cannot recall the thread where I learned that marking issues as
> resolved and not close them is sometimes very useful.
>
> For example FOR-828. I resolved this issue and not closed it since I see
> it as reference. It is an example how to fix a specific problem rather
> then a bug. Next time I am looking for information on IE failing to read
> the UTF-8 character encoding I will turn to this issue. Similar are the
> documentation issues.

Jira is very powerful, can still find issues even when closed.

Ideally that type of issue should be put into documentation,
perhaps a simple FAQ that points to that FOR-* link.

There might be some types of issues that remain open,
perhaps ongoing ones that need to be done for every release.
However in general i reckon close them when finished.

Going by the title of FOR-828 it sounds like it should
be closed.

Though a better fix would be "rm -rf InternetExploder" :-)
It is a shame that we need to bend our adherance to standards
just to suit it.

-David

> > > This leads further to the question should we better close issues instead
> > > of resolving it?
> >
> > Both.
> >
> > I just hit the Close button and it shows a Resolution option.
> > It sounds like you might be doing it in two steps:
> > Resolve then CLose.
> >
> > > Would this help that people do not reuse issues?
> >
> > Yes.
> >
> > > Maybe we should just adjust the filter and treat resolved issue as "not
> > > open" issues. That definitely will reduce my flashbacks.
> >
> > Better that you close issues.
> >
>
> ok, will do so in the future.
>
> salu2
> --
> thorsten
>
> "Together we stand, divided we fall!"
> Hey you (Pink Floyd)
>
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (10 issues)
Subscriber: rgardler


Key Summary
FOR-895 Validation issues: pelt theme
http://issues.apache.org/jira/browse/FOR-895
FOR-894 Validation issues: common theme
http://issues.apache.org/jira/browse/FOR-894
FOR-891 css-validator reports CSS errors and many warnings for pelt skin
http://issues.apache.org/jira/browse/FOR-891
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-635 images not reproduced in PDFs, if sources are in xdocs/images directory
http://issues.apache.org/jira/browse/FOR-635
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (12 issues)
Subscriber: rgardler


Key Summary
FOR-824 HowTo DTD 2.0 <a> elements not transformed correctly
http://issues.apache.org/jira/browse/FOR-824
FOR-814 Add documentation to explain how to aggregate data
http://issues.apache.org/jira/browse/FOR-814
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-525 Making views XHTML compliant
http://issues.apache.org/jira/browse/FOR-525
FOR-518 Change toolbox font in skinconf.xml for pelt
http://issues.apache.org/jira/browse/FOR-518
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-368 Add ihtml to "Deprecation of .ehtml and .ihtml" reference
http://issues.apache.org/jira/browse/FOR-368
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280
FOR-275 front-piece title page for pdf-output
http://issues.apache.org/jira/browse/FOR-275
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (12 issues)
Subscriber: rgardler


Key Summary
FOR-824 HowTo DTD 2.0 <a> elements not transformed correctly
http://issues.apache.org/jira/browse/FOR-824
FOR-814 Add documentation to explain how to aggregate data
http://issues.apache.org/jira/browse/FOR-814
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-525 Making views XHTML compliant
http://issues.apache.org/jira/browse/FOR-525
FOR-518 Change toolbox font in skinconf.xml for pelt
http://issues.apache.org/jira/browse/FOR-518
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-368 Add ihtml to "Deprecation of .ehtml and .ihtml" reference
http://issues.apache.org/jira/browse/FOR-368
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280
FOR-275 front-piece title page for pdf-output
http://issues.apache.org/jira/browse/FOR-275
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (7 issues)
Subscriber: rgardler


Key Summary
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-635 images not reproduced in PDFs, if sources are in xdocs/images directory
http://issues.apache.org/jira/browse/FOR-635
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
jira@apache.org wrote:
> Issue Subscription
> Filter: FOR-open-with-patch (12 issues)
> Subscriber: rgardler

We still seem to have two incompatible messages from JIRA. Both appear
to be set up by myself (i.e. Subscriber: rgardler).

Some time ago, before the existence of the "patch" field, I created a
filter that may well have had the same name. This filter would create
different results as it worked by assuming an attachment was a patch. I
also tried to set up a mail subscription, but this never seemed to work.

I checked this last week at Davids request and saw no second filter
called "FOR-open-with-patch", I see only one filter with a single
subscription. I also only see one FOR-* filter with a subscription, the
correct one (i.e. returns 7 issues) See [1]

Does anyone have any idea how this is happening? If I it dead silence
here I'll go to the infra@ list. Can I please request that everyone at
least looks at the filters in Jira and ensure that you can't see what is
causing this double subscription, that way I can tell infra we have done
what checks we can.

Ross

[1] http://issues.apache.org/jira/secure/ManageFilters.jspa
RE: [jira] Subscription: FOR-open-with-patch [ In reply to ]
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Monday, 12 June 2006 6:02 AM
> To: dev@forrest.apache.org
> Subject: Re: [jira] Subscription: FOR-open-with-patch
>
> jira@apache.org wrote:
> > Issue Subscription
> > Filter: FOR-open-with-patch (12 issues)
> > Subscriber: rgardler
>
> We still seem to have two incompatible messages from JIRA. Both appear
> to be set up by myself (i.e. Subscriber: rgardler).
>
> Some time ago, before the existence of the "patch" field, I created a
> filter that may well have had the same name. This filter would create
> different results as it worked by assuming an attachment was a patch. I
> also tried to set up a mail subscription, but this never seemed to work.
>
> I checked this last week at Davids request and saw no second filter
> called "FOR-open-with-patch", I see only one filter with a single
> subscription. I also only see one FOR-* filter with a subscription, the
> correct one (i.e. returns 7 issues) See [1]
>
> Does anyone have any idea how this is happening? If I it dead silence
> here I'll go to the infra@ list. Can I please request that everyone at
> least looks at the filters in Jira and ensure that you can't see what is
> causing this double subscription, that way I can tell infra we have done
> what checks we can.
>
> Ross
>
> [1] http://issues.apache.org/jira/secure/ManageFilters.jspa

I don't know why it is happening, but to confirm from the above link for me
I can see only one instance of FOR-open-with-patch - created by David
Crossley.

Everyones view of this page will show differently for the 'Your Filters'
section, i.e. - filters created by you. What does yours say.

There have been Issues with Jira in the past where filters can get hidden
but remain active if the creator of the filter is deleted, and other such
bugs.[1][2]

I am subscribed to the jira-users list, I'll do a search and see if anything
like it comes up, otherwise I'll email the problem to them and see what they
say.

I take it infra@ manage jira then do they?

Gav...

A couple of examples :-

[1] - http://jira.atlassian.com/browse/JRA-8059
[2] - http://jira.atlassian.com/browse/JRA-6561



>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.8.3/360 - Release Date: 6/9/2006
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
Gav.... wrote:
>
>>-----Original Message-----
>>From: Ross Gardler [mailto:rgardler@apache.org]
>>Sent: Monday, 12 June 2006 6:02 AM
>>To: dev@forrest.apache.org
>>Subject: Re: [jira] Subscription: FOR-open-with-patch
>>
>>jira@apache.org wrote:
>>
>>>Issue Subscription
>>>Filter: FOR-open-with-patch (12 issues)
>>>Subscriber: rgardler
>>
>>We still seem to have two incompatible messages from JIRA. Both appear
>>to be set up by myself (i.e. Subscriber: rgardler).
>>
>>Some time ago, before the existence of the "patch" field, I created a
>>filter that may well have had the same name. This filter would create
>>different results as it worked by assuming an attachment was a patch. I
>>also tried to set up a mail subscription, but this never seemed to work.
>>
>>I checked this last week at Davids request and saw no second filter
>>called "FOR-open-with-patch", I see only one filter with a single
>>subscription. I also only see one FOR-* filter with a subscription, the
>>correct one (i.e. returns 7 issues) See [1]
>>
>>Does anyone have any idea how this is happening? If I it dead silence
>>here I'll go to the infra@ list. Can I please request that everyone at
>>least looks at the filters in Jira and ensure that you can't see what is
>>causing this double subscription, that way I can tell infra we have done
>>what checks we can.
>>
>>Ross
>>
>>[1] http://issues.apache.org/jira/secure/ManageFilters.jspa
>
>
> I don't know why it is happening, but to confirm from the above link for me
> I can see only one instance of FOR-open-with-patch - created by David
> Crossley.
>
> Everyones view of this page will show differently for the 'Your Filters'
> section, i.e. - filters created by you. What does yours say.

I can't see a "Your Filters" link, where is it? I only see a "Manage
Filters" (perhaps because I am an admin?)

> There have been Issues with Jira in the past where filters can get hidden
> but remain active if the creator of the filter is deleted, and other such
> bugs.[1][2]

Ahhh... We my be hitting such a bug then.

> I am subscribed to the jira-users list, I'll do a search and see if anything
> like it comes up, otherwise I'll email the problem to them and see what they
> say.

That would be great - thanks.

> I take it infra@ manage jira then do they?

Yes, the infra@ list is where all things pertaining to ASF
infrastructure are handled.

Ross

> [1] - http://jira.atlassian.com/browse/JRA-8059
> [2] - http://jira.atlassian.com/browse/JRA-6561
RE: [jira] Subscription: FOR-open-with-patch [ In reply to ]
> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Monday, 12 June 2006 4:11 PM
> To: dev@forrest.apache.org
> Subject: Re: [jira] Subscription: FOR-open-with-patch
>
> Gav.... wrote:
> >
> >>-----Original Message-----
> >>From: Ross Gardler [mailto:rgardler@apache.org]
> >>Sent: Monday, 12 June 2006 6:02 AM
> >>To: dev@forrest.apache.org
> >>Subject: Re: [jira] Subscription: FOR-open-with-patch
> >>
> >>jira@apache.org wrote:
> >>
> >>>Issue Subscription
> >>>Filter: FOR-open-with-patch (12 issues)
> >>>Subscriber: rgardler
> >>
> >>We still seem to have two incompatible messages from JIRA. Both appear
> >>to be set up by myself (i.e. Subscriber: rgardler).
> >>
> >>Some time ago, before the existence of the "patch" field, I created a
> >>filter that may well have had the same name. This filter would create
> >>different results as it worked by assuming an attachment was a patch. I
> >>also tried to set up a mail subscription, but this never seemed to work.
> >>
> >>I checked this last week at Davids request and saw no second filter
> >>called "FOR-open-with-patch", I see only one filter with a single
> >>subscription. I also only see one FOR-* filter with a subscription, the
> >>correct one (i.e. returns 7 issues) See [1]
> >>
> >>Does anyone have any idea how this is happening? If I it dead silence
> >>here I'll go to the infra@ list. Can I please request that everyone at
> >>least looks at the filters in Jira and ensure that you can't see what is
> >>causing this double subscription, that way I can tell infra we have done
> >>what checks we can.
> >>
> >>Ross
> >>
> >>[1] http://issues.apache.org/jira/secure/ManageFilters.jspa
> >
> >
> > I don't know why it is happening, but to confirm from the above link for
> me
> > I can see only one instance of FOR-open-with-patch - created by David
> > Crossley.
> >
> > Everyones view of this page will show differently for the 'Your Filters'
> > section, i.e. - filters created by you. What does yours say.
>
> I can't see a "Your Filters" link, where is it? I only see a "Manage
> Filters" (perhaps because I am an admin?)

Possibly, or because you have not set up any specific filters for you - I
have set one up and so I presume if I delete it the section will disappear -
- er, just done that, nope the section is still there. Under 'Manage
Filters' I have a section called 'Your Filters' and under that one called
'Viewable Filters' .

So it could be that because you are Admin you have no need for such a
section (don't see why not though!)

Also, having a section called 'Viewable Filters' makes me think there must
also be a section somewhere where 'Hidden Filters' may exist. And our
duplicate may live there. I am guessing, I am no expert in the Admin of
Jira, I did download it for evaluation but could not afford the licence, so
bought something cheaper for my purposes instead.

>
> > There have been Issues with Jira in the past where filters can get
> hidden
> > but remain active if the creator of the filter is deleted, and other
> such
> > bugs.[1][2]
>
> Ahhh... We my be hitting such a bug then.
>
> > I am subscribed to the jira-users list, I'll do a search and see if
> anything
> > like it comes up, otherwise I'll email the problem to them and see what
> they
> > say.
>
> That would be great - thanks.

I have emailed jira-users and will forward on the reply.

>
> > I take it infra@ manage jira then do they?
>
> Yes, the infra@ list is where all things pertaining to ASF
> infrastructure are handled.

Ok, cool.

Gav...

>
> Ross
>
> > [1] - http://jira.atlassian.com/browse/JRA-8059
> > [2] - http://jira.atlassian.com/browse/JRA-6561
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
Gav.... wrote:
>
>>-----Original Message-----
>>From: Ross Gardler [mailto:rgardler@apache.org]
>>Sent: Monday, 12 June 2006 4:11 PM
>>To: dev@forrest.apache.org
>>Subject: Re: [jira] Subscription: FOR-open-with-patch
>>
>>Gav.... wrote:
>>
>>>>-----Original Message-----
>>>>From: Ross Gardler [mailto:rgardler@apache.org]
>>>>Sent: Monday, 12 June 2006 6:02 AM
>>>>To: dev@forrest.apache.org
>>>>Subject: Re: [jira] Subscription: FOR-open-with-patch
>>>>
>>>>jira@apache.org wrote:
>>>>
>>>>
>>>>>Issue Subscription
>>>>>Filter: FOR-open-with-patch (12 issues)
>>>>>Subscriber: rgardler
>>>>
>>>>We still seem to have two incompatible messages from JIRA. Both appear
>>>>to be set up by myself (i.e. Subscriber: rgardler).
>>>>
>>>>Some time ago, before the existence of the "patch" field, I created a
>>>>filter that may well have had the same name. This filter would create
>>>>different results as it worked by assuming an attachment was a patch. I
>>>>also tried to set up a mail subscription, but this never seemed to work.
>>>>
>>>>I checked this last week at Davids request and saw no second filter
>>>>called "FOR-open-with-patch", I see only one filter with a single
>>>>subscription. I also only see one FOR-* filter with a subscription, the
>>>>correct one (i.e. returns 7 issues) See [1]
>>>>
>>>>Does anyone have any idea how this is happening? If I it dead silence
>>>>here I'll go to the infra@ list. Can I please request that everyone at
>>>>least looks at the filters in Jira and ensure that you can't see what is
>>>>causing this double subscription, that way I can tell infra we have done
>>>>what checks we can.
>>>>
>>>>Ross
>>>>
>>>>[1] http://issues.apache.org/jira/secure/ManageFilters.jspa
>>>
>>>
>>>I don't know why it is happening, but to confirm from the above link for
>>
>>me
>>
>>>I can see only one instance of FOR-open-with-patch - created by David
>>>Crossley.
>>>
>>>Everyones view of this page will show differently for the 'Your Filters'
>>>section, i.e. - filters created by you.

...

> Under 'Manage
> Filters' I have a section called 'Your Filters' and under that one called
> 'Viewable Filters' .

I see it now - thanks. Nothing in there indicating the rogue filter exists.

> Also, having a section called 'Viewable Filters' makes me think there must
> also be a section somewhere where 'Hidden Filters' may exist. And our
> duplicate may live there.

I think "viewable filters" are ones you have the privs to view, i.e. you
are a member of the project. Since I'm an admin I should be able to see
all the filters, but can only see the one FOR-open-with-patch created by
David.

We'll have to see if your email to the Jira Users list comes up with
anything.

Ross
RE: [jira] Subscription: FOR-open-with-patch [ In reply to ]
Neil Applebaum replies :-

Does your admin have access to run a SQL Query on your database?

Just run "select * from jira.filtersubscription" and you'll see the owner of
the filter (as the username)

- Neal -

HTH

Gav...

> -----Original Message-----
> From: Ross Gardler [mailto:rgardler@apache.org]
> Sent: Monday, 12 June 2006 8:09 PM
> To: dev@forrest.apache.org
> Subject: Re: [jira] Subscription: FOR-open-with-patch
>
> Gav.... wrote:
> >
> >>-----Original Message-----
> >>From: Ross Gardler [mailto:rgardler@apache.org]
> >>Sent: Monday, 12 June 2006 4:11 PM
> >>To: dev@forrest.apache.org
> >>Subject: Re: [jira] Subscription: FOR-open-with-patch
> >>
> >>Gav.... wrote:
> >>
> >>>>-----Original Message-----
> >>>>From: Ross Gardler [mailto:rgardler@apache.org]
> >>>>Sent: Monday, 12 June 2006 6:02 AM
> >>>>To: dev@forrest.apache.org
> >>>>Subject: Re: [jira] Subscription: FOR-open-with-patch
> >>>>
> >>>>jira@apache.org wrote:
> >>>>
> >>>>
> >>>>>Issue Subscription
> >>>>>Filter: FOR-open-with-patch (12 issues)
> >>>>>Subscriber: rgardler
> >>>>
> >>>>We still seem to have two incompatible messages from JIRA. Both appear
> >>>>to be set up by myself (i.e. Subscriber: rgardler).
> >>>>
> >>>>Some time ago, before the existence of the "patch" field, I created a
> >>>>filter that may well have had the same name. This filter would create
> >>>>different results as it worked by assuming an attachment was a patch.
> I
> >>>>also tried to set up a mail subscription, but this never seemed to
> work.
> >>>>
> >>>>I checked this last week at Davids request and saw no second filter
> >>>>called "FOR-open-with-patch", I see only one filter with a single
> >>>>subscription. I also only see one FOR-* filter with a subscription,
> the
> >>>>correct one (i.e. returns 7 issues) See [1]
> >>>>
> >>>>Does anyone have any idea how this is happening? If I it dead silence
> >>>>here I'll go to the infra@ list. Can I please request that everyone at
> >>>>least looks at the filters in Jira and ensure that you can't see what
> is
> >>>>causing this double subscription, that way I can tell infra we have
> done
> >>>>what checks we can.
> >>>>
> >>>>Ross
> >>>>
> >>>>[1] http://issues.apache.org/jira/secure/ManageFilters.jspa
> >>>
> >>>
> >>>I don't know why it is happening, but to confirm from the above link
> for
> >>
> >>me
> >>
> >>>I can see only one instance of FOR-open-with-patch - created by David
> >>>Crossley.
> >>>
> >>>Everyones view of this page will show differently for the 'Your
> Filters'
> >>>section, i.e. - filters created by you.
>
> ...
>
> > Under 'Manage
> > Filters' I have a section called 'Your Filters' and under that one
> called
> > 'Viewable Filters' .
>
> I see it now - thanks. Nothing in there indicating the rogue filter
> exists.
>
> > Also, having a section called 'Viewable Filters' makes me think there
> must
> > also be a section somewhere where 'Hidden Filters' may exist. And our
> > duplicate may live there.
>
> I think "viewable filters" are ones you have the privs to view, i.e. you
> are a member of the project. Since I'm an admin I should be able to see
> all the filters, but can only see the one FOR-open-with-patch created by
> David.
>
> We'll have to see if your email to the Jira Users list comes up with
> anything.
>
> Ross
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
I did some more investigation. Looking at the hidden email
headers, i see that the incorrect one comes from an older
installation of the ASF Jira. It moved machines a few
weeks ago. I have sent email to infra.

-David
Re: [jira] Subscription: FOR-open-with-patch [ In reply to ]
David Crossley wrote:
> I did some more investigation. Looking at the hidden email
> headers, i see that the incorrect one comes from an older
> installation of the ASF Jira. It moved machines a few
> weeks ago. I have sent email to infra.

Well spotted David. I didn't see that. So it must be that the filter I
set up around 12 months ago suddenly started working.

Ross
[jira] Subscription: FOR-open-with-patch [ In reply to ]
Issue Subscription
Filter: FOR-open-with-patch (7 issues)
Subscriber: rgardler


Key Summary
FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin
http://issues.apache.org/jira/browse/FOR-811
FOR-795 Navigation bars for easy access in long documents
http://issues.apache.org/jira/browse/FOR-795
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
http://issues.apache.org/jira/browse/FOR-652
FOR-635 images not reproduced in PDFs, if sources are in xdocs/images directory
http://issues.apache.org/jira/browse/FOR-635
FOR-412 use CSS for displaying list of Changes
http://issues.apache.org/jira/browse/FOR-412
FOR-311 OOo Headings bug causes Forrest to fail
http://issues.apache.org/jira/browse/FOR-311
FOR-280 gather index terms from documents to create index page with links
http://issues.apache.org/jira/browse/FOR-280

1 2 3  View All