[
https://issues.apache.org/jira/browse/OFBIZ-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596625#comment-14596625
]
Jacques Le Roux commented on OFBIZ-5035:
I think you should already create a new J
[
https://issues.apache.org/jira/browse/OFBIZ-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596595#comment-14596595
]
Jacques Le Roux commented on OFBIZ-6237:
I can't remember why I did remove the "ol
[
https://issues.apache.org/jira/browse/OFBIZ-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-6237.
--
Resolution: Fixed
Fix Version/s: Upcoming Branch
13.07.03
+1
Nicolas
Le 22/06/2015 10:04, Sharan-F a écrit :
Hi Everyone
One issue that came up in the Community Day last Saturday was related to
Jira profile permissions. A while ago Pierre trialled the use of the
'Contributor' group permission within Jira. This group has additional
permissions to assi
Depending of the context.
If is a bug fix without activity, the reassign is good !
But in many case, and for my assigned issue fell free to reassign ;)
You are sure that a read the making modifications.
Nicolas
Le 22/06/2015 10:10, Sharan-F a écrit :
Hi Everyone
Another topic that came up on
How strenuous is it to apply some common decency and ask up front up if
assignment can be transferred? Maybe the Assignee forgot to update the
status of the issue. Maybe something else interfered. Our JIRA issues are
commonly not of the nature that changes need to be persisted fast.
Community over
I think that in a community based Bugtracker, everyone can work on any
bug. A ticket is not under someone property, the assign attribute exists
to say that we intend to work on it.
There is no problem to work on an already assigned Jira, and provide
patch. Collaborating to get the best solutio
+1. Nice move. PDFBox did this before, and then we saw Tilman Hausherr's great
contributions.
在 2015-6-22，下午4:04，Sharan-F 写道：
> Hi Everyone
>
> One issue that came up in the Community Day last Saturday was related to
> Jira profile permissions. A while ago Pierre trialled the use of the
> 'Co
+1
I agree that every contributor should be in "Contributor" group :) !
Gil
On 22/06/2015 10:04, Sharan-F wrote:
Hi Everyone
One issue that came up in the Community Day last Saturday was related to
Jira profile permissions. A while ago Pierre trialled the use of the
'Contributor' group permis
Maybe "Work in Progress" status would show the assigne is still working on it.
Of course then if it has been obviously forgotten (no visible work for several days, weeks, months depending on the importance of the issue) then
asking a question if it could be reassigned would be the better way IMO.
+1
Jacques
Le 22/06/2015 10:36, Michael Brohl a écrit :
+1
Thanks and regards,
Michael
Am 22.06.15 um 10:04 schrieb Sharan-F:
Hi Everyone
One issue that came up in the Community Day last Saturday was related to
Jira profile permissions. A while ago Pierre trialled the use of the
'Contribut
[
https://issues.apache.org/jira/browse/OFBIZ-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-6511:
Issue Type: Improvement (was: New Feature)
> Geos have a lifespan
>
>
>
Thanks Adrian for reporting this. I am looking into this and will get back
as soon as possible.
Thanks
--
Divesh Dutta.
On Sat, Jun 20, 2015 at 10:26 PM, Adrian Crum <
adrian.c...@sandglass-software.com> wrote:
> This commit generates this error:
>
> 2015-06-20 09:42:56,054 |delegator-startup-1
Thanks Deepak. Will change the code accordingly.
Thanks
--
Divesh Dutta.
On Sun, Jun 21, 2015 at 10:40 AM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:
> Please do not use javolution classes.
>
> Thanks & Regards
> --
> Deepak Dixit
>
> On Saturday, June 20, 2015, wrote:
>
> > Author:
[
https://issues.apache.org/jira/browse/OFBIZ-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lilian Iatco updated OFBIZ-6506:
Labels: display entity form ofbiz screen vulnerability xss (was: entity
form xss)
> XSS vulnerabil
Hi Sharan,
I think it depends...
If it is visible that the current assignee is actively working on the
topic (active discussions etc.) I would at least ask him if it is ok to
take over the issue.
If it is visible that the issue is not actively worked on and someone
else has the time to take
+1
Thanks and regards,
Michael
Am 22.06.15 um 10:04 schrieb Sharan-F:
Hi Everyone
One issue that came up in the Community Day last Saturday was related to
Jira profile permissions. A while ago Pierre trialled the use of the
'Contributor' group permission within Jira. This group has additional
Hi Everyone
Another topic that came up on the Community Day was whether a developer
could pick up a Jira issue already assigned to someone else.
At the moment I don't think we have any indication to show whether the
original assignee wants to keep the issue (e.g. they are already part way
through
Hi Everyone
One issue that came up in the Community Day last Saturday was related to
Jira profile permissions. A while ago Pierre trialled the use of the
'Contributor' group permission within Jira. This group has additional
permissions to assign themselves to an issue (e.g. while they are preparin
Reporter: Shi Jinghai
>Assignee: Shi Jinghai
>Priority: Minor
> Fix For: Trunk
>
> Attachments: OFBiz-6518-applications-20150622.patch,
> OFBiz-6518-framework-20150622.patch, OFBiz-6518-specialpurpose-20150622.patch
>
> Original Estimate: 48
20 matches
Mail list logo
