Combination View Flat View Tree View
Threads [ Previous | Next ]
Showing 41 - 48 of 48 results.
of 3
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
March 27, 2013 9:06 PM
Answer

James Falkner

Community Moderator

Rank: Liferay Legend

Posts: 1406

Join Date: September 17, 2010

Recent Posts

Aniceto P Madrid:
James

Sometimes, issues reported seem to be important but if they are badly reported and not watched by the reporter, that issue is suggested to be closed after 10 days of inactivity. I think Liferay is losing important feedback from their users, and that is bad. I suggest that reported should be automatically added to the watch list and that he or she cannot unwatch. I don't remember if there is a policy agreement when somebody signs in JIRA, but it should be added this watching feature.

And now I suggest to run an script to add all reporters to the watch list of his/her issues. At least Liferay transmits a message to JIRA users: your issue is being attended, late, but not completely ignored.

Aniceto


When a person files an issue, they are known as the 'Reporter' and are automatically 'watching' the issue and will receive notification when the issue is commented on or updated in any way, and they cannot un-do this (of course, they could ignore emails or, for example, change jobs and their old email isn't properly forwarded).

So, for a bug report which no one can understand or act on due to missing or confusing info, if the reporter isn't around to clarify things, should the issue remain open? I don't see how it would ever be able to be closed, since it can't be fixed, and the reporter is no longer responding.
Aniceto P Madrid
RE: Liferay 6.2 Milestone 4: Community Verifier
March 28, 2013 3:39 AM
Answer

Aniceto P Madrid

Rank: Regular Member

Posts: 135

Join Date: May 24, 2008

Recent Posts

James

I thought that reporter only received by email notifications when she or he adds oneself to the watch list. If after every change the reporter is always notified even if he has not added oneself to the watch list, then everything is fine.

I suggested this because I've found many issues with no watchers and after a comment asking for clarification I don't receive any response. So, according to instructions, after 10 days of no response I ask for closing the issue due to reporter inactivity.

Aniceto
Mika Koivisto
RE: Liferay 6.2 Milestone 4: Community Verifier
April 1, 2013 11:08 AM
Answer

Mika Koivisto

LIFERAY STAFF

Rank: Liferay Legend

Posts: 1513

Join Date: August 7, 2006

Recent Posts

Reporter will always get notifications without adding themselves as watcher. Also if the issue is assigned to you you'll get notifications but only as long as it's assigned to you. In all other cases you need to be a watcher on the issue to get notifications.
Aniceto P Madrid
RE: Liferay 6.2 Milestone 4: Community Verifier
April 6, 2013 2:48 AM
Answer

Aniceto P Madrid

Rank: Regular Member

Posts: 135

Join Date: May 24, 2008

Recent Posts

The link to the issues query http://issues.liferay.com/secure/IssueNavigator.jspa?mode=hide&requestId=16625 no longer works. It seems businessValue is never now null. So no issues are listed. Please, update the query or the link in the Community Verifier page.

Thanks
James Falkner
Re: [Liferay Forums][Community Verifier Team] RE: Liferay 6.2 Milestone 4:
April 6, 2013 9:51 AM
Answer

James Falkner

Community Moderator

Rank: Liferay Legend

Posts: 1406

Join Date: September 17, 2010

Recent Posts

Will do... Some changes to the business value field occurred on Friday. Thanks for the heads-up!

-jhf-

On Apr 6, 2013, at 5:48 AM, "Aniceto P Madrid from liferay.com" <forums@liferay.com> wrote:

> The link to the issues query http://issues.liferay.com/secure/IssueNavigator.jspa?mode=hide&requestId=16625 no longer works. It seems businessValue is never now null. So no issues are listed. Please, update the query or the link in the Community Verifier page.
>
> Thanks
>
>
> To view the thread, follow the link below:
> http://www.liferay.com/community/forums/-/message_boards/view_message/23393352
> --
> Thanks, Liferay.com Forums
Mika Koivisto
RE: Liferay 6.2 Milestone 4: Community Verifier
April 8, 2013 11:36 AM
Answer

Mika Koivisto

LIFERAY STAFF

Rank: Liferay Legend

Posts: 1513

Join Date: August 7, 2006

Recent Posts

I fixed the issue.
Aniceto P Madrid
RE: Liferay 6.2 Milestone 4: Community Verifier
May 18, 2013 4:30 AM
Answer

Aniceto P Madrid

Rank: Regular Member

Posts: 135

Join Date: May 24, 2008

Recent Posts

As of release of 6.2.0m5, Should remaining issues be checked against m5 or is this round closed?

By the way, release of 6.1 GA3 is taking a lot more than expected.
James Falkner
RE: Liferay 6.2 Milestone 4: Community Verifier
May 18, 2013 7:18 AM
Answer

James Falkner

Community Moderator

Rank: Liferay Legend

Posts: 1406

Join Date: September 17, 2010

Recent Posts

Aniceto P Madrid:
As of release of 6.2.0m5, Should remaining issues be checked against m5 or is this round closed?

By the way, release of 6.1 GA3 is taking a lot more than expected.



Excellent question, Aniceto... yes, the remaining should be checked against m5 - because some of them may have been fixed.

Yes, GA3 is taking longer than expected - I'm sorry it's taking so long, we played a little game of backporting fixes from trunk to 6.1, then backporting some more, then some more, .... I *really* hope we can have it completed and shipped in the June/July timeframe, but I am no longer giving any estimates emoticon

BTW, we took the PACL requirement off of Marketplace (partly because GA3 is taking longer than expected). So for those apps that otherwise worked, they can now happily live in Marketplace.

Also, for those looking forward to your CV rewards emoticon Rest assured I have not and will not forget about the certificates, tee shirts, and training/symposium offer. I will follow up in a separate thread with the details. Aniceto gets the gold star for contribution here, but all of you contributed in some way! Thanks everyone!
Showing 41 - 48 of 48 results.
of 3