This was now resolved by Atlassian support. Thanks all!
On Fri, 2 Nov 2018 at 10:46, Sanne Grinovero wrote:
>
> Hi all,
>
> I'm receiving requests to approve people who are creating accounts on JIRA.
>
> While it's good to see lots of people interested in registering, I've
> never had to approve
Hi,
Not sure it's related but when I go to JIRA on my mobile phone (probably
not logged in), I have a popup asking to log in that I have to close.
Sometimes it reappears once again when I close it.
I don't have this behavior when using Firefox on my laptop, even when
signed out but that might exp
Sanne -
Same here, I haven't changed anything.
Chris
On 11/2/18 7:14 AM, Yoann Rodiere wrote:
> I didn't change the settings recently.
>
> On Fri, 2 Nov 2018 at 12:03, Sanne Grinovero wrote:
>
>> Hi all,
>>
>> I'm receiving requests to approve people who are creating accounts on JIRA.
>>
>> Whi
Hi,
I didn't change the settings recently.
Yoann Rodière
Hibernate NoORM Team
yo...@hibernate.org
On Fri, 2 Nov 2018 at 12:03, Sanne Grinovero wrote:
> Hi all,
>
> I'm receiving requests to approve people who are creating accounts on JIRA.
>
> While it's good to see lots of people interested
Hi all,
I'm receiving requests to approve people who are creating accounts on JIRA.
While it's good to see lots of people interested in registering, I've
never had to approve these before.
Did someone change settings or should I report this to Atlassian?
Thanks,
Sanne
__
Interesting... That is still the permission in the settings. But for
some reason I cannot. I do not think the issue was closed, but honestly
its now been a few days and I forget which issue it is :(
On Thu, Oct 18, 2018 at 6:45 AM Sanne Grinovero wrote:
> On Thu, 18 Oct 2018 at 12:39, Steve Eb
On Thu, 18 Oct 2018 at 12:39, Steve Ebersole wrote:
>
> For sure it *was* allowed for years ;)
Ok, maybe it was just in my mind, but because of that I never tried so
I would never have noticed any change :)
For sure I didn't reconfigure that myself.
>
> Initially I set up the permissions that a
For sure it *was* allowed for years ;)
Initially I set up the permissions that a user could edit their own
comments. I think admins could edit any, but I do not remember that part
for sure.
On Thu, Oct 18, 2018 at 5:17 AM Sanne Grinovero wrote:
>
> I can't remember ever being allowed to edit c
I can't remember ever being allowed to edit comments.
For sure it wasn't allowed years back, I don't honestly know about recent
times as I never tried - probably having been coached by the old rule :)
On Thu, 18 Oct 2018, 11:06 Steve Ebersole, wrote:
> Did someone remove the ability to edit on
I think this happens when a Jira is closed.
On Wed, 17 Oct 2018 at 17:27, Steve Ebersole wrote:
> The elipse is there but the only option is Permalink
>
>
> On Wed, Oct 17, 2018, 9:53 AM Chris Cranford wrote:
>
> > Steve -
> >
> > I have the option for my user. Is the ellipsis button not showi
The elipse is there but the only option is Permalink
On Wed, Oct 17, 2018, 9:53 AM Chris Cranford wrote:
> Steve -
>
> I have the option for my user. Is the ellipsis button not showing up
> for you on the comment?
>
> On 10/17/18 9:12 AM, Steve Ebersole wrote:
> > Did someone remove the abilit
Steve -
I have the option for my user. Is the ellipsis button not showing up
for you on the comment?
On 10/17/18 9:12 AM, Steve Ebersole wrote:
> Did someone remove the ability to edit one's comments? I added a comment I
> would like to adjust syntax (code fragment), but Jira will not let me
__
Did someone remove the ability to edit one's comments? I added a comment I
would like to adjust syntax (code fragment), but Jira will not let me
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hiberna
Top right of the page, click "Configure release notes", select "text" in
"Please select style", there will be a textarea to the bottom of the page
with the text-formatted release notes.
OR add "&styleName=Text&Create=Create" to the URL of the release notes.
See for instance
https://hibernate.atlas
Anyone know what happened to the ability to export release notes in text
format from Jira? When I click on a version's release notes it takes me to
the HTML format which it always did, but there is no longer an option to
choose the text format
___
hibern
Yes labels and tags would help me to keep them "out of the way" but
like Yoann suggests, I expect the "contrib repository" to not be
released and tagged in strict synch with the Hibernate OGM main
project?
I guess we didn't discuss this in depth, but if we don't allow the
"contrib repository" to f
I would prefer to release both at the same time even if there are no
big changes.
As for creating a new project, wouldn't have a new label or component be enough?
On Fri, Mar 17, 2017 at 8:21 AM, Yoann Rodiere wrote:
> Isn't marking those as "New feature" enough? Or, if necessary, tagging them?
Isn't marking those as "New feature" enough? Or, if necessary, tagging them?
I obviously can't tell how others use JIRA, but personally I don't dive
into old tickets every day. Most of the time I only check the new
(incoming) tickets and those assigned to the next release. So, those extra
tickets a
There are more than 300 open issues, which is fine but rather than
being these well-defined issues most sound like wishful thinking of
someone having a (possibly cool) idea but not really executing on it.
Since JIRA is an issue tracker and not really a planning tool / note
taking app I wish we cou
Hello,
What about backporting the JCache module?
Since JCache is Java 1.6, that could make it available to more users.
I believe there have been small API changes between 5.1 and 5.2 but still
the porting should be easy enough and I am willing to help for that.
Regards,
Louis
On Tue, Jun 7, 2016
Hi,
Because 5.1 is the last version supporting 1.6, I think it's worth to
integrate as many fixes as we can that are now only available on the 5.2
branch.
Therefore, I collected a list of issues so that you can tell me which ones
you'd like me to cherry pick on 5.1:
https://hibernate.atlassian.n
On 4 May 2016 at 11:06, Gunnar Morling wrote:
> E.g. that one: https://hibernate.atlassian.net/projects/HSEARCH/summary
>
> The first icon on the left side (with the Hibernate logo) links to this. Do
> you see the activity feed when clicking on in and not being logged in?
Ok, no I see an error in
E.g. that one: https://hibernate.atlassian.net/projects/HSEARCH/summary
The first icon on the left side (with the Hibernate logo) links to this. Do
you see the activity feed when clicking on in and not being logged in?
2016-05-04 12:03 GMT+02:00 Sanne Grinovero :
> On 4 May 2016 at 10:56, Gunnar
On 4 May 2016 at 10:56, Gunnar Morling wrote:
> Hi there,
>
> This is still an issue: when not being logged, an error instead of the
> activity dashboard is shown in JIRA.
I don't see such an error. Are you maybe looking at an URL which isn't
the typical welcome page?
Thanks,
Sanne
>
> Davide,
I'll have a look.
Davide
On Wed, May 4, 2016 at 10:56 AM, Gunnar Morling
wrote:
> Hi there,
>
> This is still an issue: when not being logged, an error instead of the
> activity dashboard is shown in JIRA.
>
> Davide, as master of tools, could you look into this?
>
> Coming as a new user to JIR
Hi there,
This is still an issue: when not being logged, an error instead of the
activity dashboard is shown in JIRA.
Davide, as master of tools, could you look into this?
Coming as a new user to JIRA and seeing such error isn't a great experience.
Thanks,
--Gunnar
2016-01-14 8:02 GMT+01:00
A heads up that Atlassian will sometime soon be restarting the Jira
instance to fix the 500 errors when accessing project pages.
They are aware of the problem and are awaiting a proper fix, but in the
meantime they believe a restart will solve the problem in the short term.
___
Although not related to the issue, can someone add more rights to my JIRA
account, at least to edit my own posts.
Vlad
On Thu, Jan 14, 2016 at 9:02 AM, Gunnar Morling
wrote:
> Hi,
>
> When not being logged into JIRA, I am getting an error when opening
> the "Activity" view in JIRA, e.g. at
> ht
Hi,
When not being logged into JIRA, I am getting an error when opening
the "Activity" view in JIRA, e.g. at
https://hibernate.atlassian.net/projects/HV/summary:
"This gadget cannot be displayed on your dashboard. This could be
due to a licensing problem or an application error."
Anyone know
I have been noticing that the "GitHub link" in Jira is no longer
automatically performing syncs. I have asked Atlassian about it. In the
meantime, if you use that feature (commit linking, PR linking, etc) you
will have to manually force a sync in Jira
_
We really no longer maintain ORM 4.x. Yet we still get Jira reports citing
4.x as the affected version. We have been asking the reporter to reproduce
with 5.0.
But in the interim it is easy to lose track of these issues. Ultimately
the "affects version" needs to be updated or the issue rejected
On Mon, Mar 09, 2015 at 09:26:34PM -0500, Steve Ebersole wrote:
> I tried using the feedback approach with Atlassian, lets see how that goes
> and whether we hear back. If I don't hear back in a few days, I will reach
> out to them directly.
+1 I guess this is related to their latest changes. May
I tried using the feedback approach with Atlassian, lets see how that goes
and whether we hear back. If I don't hear back in a few days, I will reach
out to them directly.
On Mon, Mar 9, 2015 at 5:35 PM, Steve Ebersole wrote:
> Ok, if I log out I get the same. We'll have to reach out to Atla
Ok, if I log out I get the same. We'll have to reach out to Atlassian
about this. Or maybe there is a setting as to whether this should be
publicly available.
On Mon, Mar 9, 2015 at 5:29 PM, Hardy Ferentschik
wrote:
> On Mon, Mar 09, 2015 at 05:13:14PM -0500, Steve Ebersole wrote:
> > Interest
On Mon, Mar 09, 2015 at 05:13:14PM -0500, Steve Ebersole wrote:
> Interesting. I can get to that link from your email (just clicked it) just
> fine.
Turns out, I can get to these links as well - provided I am logged in.
I think my session must had expired and I was not logged in when I tried.
I
Interesting. I can get to that link from your email (just clicked it) just
fine.
On Mon, Mar 9, 2015 at 4:52 PM, Hardy Ferentschik
wrote:
> Hi,
>
> I seem to have problems with Jira atm. If I select a link which refers to
> a specific version
> (eg https://hibernate.atlassian.net/projects/OGM/v
Hi,
I seem to have problems with Jira atm. If I select a link which refers to a
specific version
(eg https://hibernate.atlassian.net/projects/OGM/versions/19251), I keep
getting a 500 error
with the message "Sorry, we had some technical problems during your last
operation."
It does not seem to
Because the automated integration doesn't work at all if you rebase.
I've considered disabling that JIRA plugin.. for now I'm hoping it
will improve in future.
On 6 November 2014 15:26, Hardy wrote:
> OOI, why do you still add the pull request links manually to Jira. It's
> nicely and automatical
Have not not had a chance to look deeply yet, but interesting...
https://confluence.atlassian.com/display/AOD/Advanced+workflow+configuration?utm_campaign=yuX3vawa&utm_medium=navbar&utm_source=inproduct
___
hibernate-dev mailing list
hibernate-dev@lists.
No, it should happen automatically. *Should* :) This new round of DVCS
support has been far from smooth. I blame it on Atlassian being in the
DVCS game now with Stash. I don't think its hard to see that they focus
their DVCS testing there rather than GitHub.
On Wed, Apr 9, 2014 at 9:46 AM, Sa
Nice, thanks Steve.
Do I need to change something in project configuration to benefit from
the automatic linking?
On 9 April 2014 13:37, Steve Ebersole wrote:
> Just a heads up that as or tomorrow (April 10) we should see the Jira /
> GitHub issues resolved. The last 2 issues we have been waitin
Just a heads up that as or tomorrow (April 10) we should see the Jira /
GitHub issues resolved. The last 2 issues we have been waiting on were
just resolved:
1) https://jira.atlassian.com/browse/DCON-391
2) https://jira.atlassian.com/browse/DCON-393
Essentially this most recent problem has been
The one reason I am leery of relying solely on autowatch (and dropping
participants) is that I am pretty sure that autowatch is not
retro-active. Meaning if you have commented on a issue and have been
receiving continuing notifications there is a danger you will no longer
get notifications. U
On 25 Jan 2013, at 1:41 PM, Steve Ebersole wrote:
> testcase reminder should be fixed now.
Thanks. Works.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
testcase reminder should be fixed now.
On Mon 25 Mar 2013 07:28:13 AM CDT, Steve Ebersole wrote:
> The field collects "participants" (creator, assignee, commenters).
> There is then a rule in the notification scheme which says that all
> participants should get notified.
>
> Autowatch is a little
The field collects "participants" (creator, assignee, commenters).
There is then a rule in the notification scheme which says that all
participants should get notified.
Autowatch is a little different than. Autowatch says to add a person
to the issue's watcher list when they comment on an iss
On 24 Jan 2013, at 8:25 PM, Steve Ebersole wrote:
> I am looking into the problem of hibernate-issues no longer getting Jira
> notifications. One possible reason is the use of the custom
> "Participants" field in our notification scheme. I am wondering if we
> ought to remove that rule from
I am looking into the problem of hibernate-issues no longer getting Jira
notifications. One possible reason is the use of the custom
"Participants" field in our notification scheme. I am wondering if we
ought to remove that rule from the notification scheme. Atlassian have
added an "autowatch
Sorry I missed this. you're welcome to restart any time, from my part
at least I'm done for today.
Cheers,
Sanne
On 13 February 2013 17:23, Steve Ebersole wrote:
> Hardy was on IRC yesterday when we dealt with the 661 emails :)
>
> Anyway, Atlassian believe this might be a "known issue" (though
Hardy was on IRC yesterday when we dealt with the 661 emails :)
Anyway, Atlassian believe this might be a "known issue" (though they
gave no pointers to references) and that the current solution is a
restart. Our restarts seem to be pretty quick, so any objections to
having them do the restart
On 13 February 2013 15:31, Hardy Ferentschik wrote:
>
> On 13 Jan 2013, at 4:26 PM, Sanne Grinovero wrote:
>
>> @Hardy I see there is a one-off specific rule to send you an
>> individual email for any issue creation, I removed that as it
>> shouldn't be needed anymore?
>
> Thanks. I want to keep
On 13 Jan 2013, at 4:26 PM, Sanne Grinovero wrote:
> @Hardy I see there is a one-off specific rule to send you an
> individual email for any issue creation, I removed that as it
> shouldn't be needed anymore?
Thanks. I want to keep getting creation emails. Then I can decide what to do.
I think
Since any JIRA change will trigger an email to
hibernate-iss...@lists.jboss.org, and JIRA can't possibly know who is
on this list, I'm getting many duplicates.
I like the fine-grained level on the mailing list as it's a safe
backup & log to inspect all events, still the volume is forcing me to
fil
Hi,
You're probably already aware of it but just in case...
I can't login to Hibernate JIRA. It looks like the server is out of disk space:
com.atlassian.crowd.embedded.ofbiz.db.DataAccessException:
org.ofbiz.core.entity.GenericEntityException: while inserting:
[GenericEntity:UserAttribute][lower
We hit that earlier too. Steve submitted a support ticket a bit ago.
- Original Message -
From: "Hardy Ferentschik"
To: "Hibernate"
Sent: Wednesday, November 7, 2012 1:50:47 PM
Subject: [hibernate-dev] Jira is not feeling well
Seems Jira is not feeling well. Nic
Seems Jira is not feeling well. Nice stack trace though:
An error occurred whilst rendering this message. Please contact the
administrators, and inform them of this bug. Details: ---
org.apache.velocity.exception.MethodInvocationException: Invocation of method
'getIssueCountByFixForVersion'
Ok, Atlassian think the reason pushed commits do not show up sometimes
is because of this:
https://studio.atlassian.com/browse/BBC-232
Essentially anytime there is a large gap between the commit date/time
and push date/time. Seems to fit the pattern I have witnessed between
(a) pull requests
Very nice!
thanks Steve
Sanne
On 7 September 2012 02:16, Steve Ebersole wrote:
> Hey everyone. A few months ago we had moved Hibernate Jira from using
> FishEye to link in commits against GitHub to using Atlassian's "DVCS
> Connector" plugin. Not even sure how many of you were aware but we had
Hey everyone. A few months ago we had moved Hibernate Jira from using
FishEye to link in commits against GitHub to using Atlassian's "DVCS
Connector" plugin. Not even sure how many of you were aware but we had
been having a few problems with it (mainly not all commits showing up
automatically).
Try that search field now, it's less than amazing ;)
On Sep 5, 2012 12:48 AM, "Gail Badner" wrote:
>
> - Original Message -
> > From: "Steve Ebersole"
> > To: "Hibernate hibernate-dev"
> > Sent: Tuesday, September 4, 20
- Original Message -
> From: "Steve Ebersole"
> To: "Hibernate hibernate-dev"
> Sent: Tuesday, September 4, 2012 1:16:55 PM
> Subject: [hibernate-dev] Jira issue links
>
> Saw something pretty cool today in Jira. Not sure when it was added,
> b
Saw something pretty cool today in Jira. Not sure when it was added,
but you can now link Jira issues to random urls.
For example, here is an issue I linked to its JBPAPP counterpart :
https://hibernate.onjira.com/browse/HHH-7563
Was thinking we might want to do that for GitHub pull-requests a
Ok, should be back now.
It does need to get restarted a little later to perform an upgrade due
to Atlassian's latest security advisory.
On Tue 28 Aug 2012 08:45:32 AM CDT, Steve Ebersole wrote:
> The Hibernate Jira is not feeling well today :)
>
> I have notified Atlassian/Contegix. We should
The Hibernate Jira is not feeling well today :)
I have notified Atlassian/Contegix. We should hear shortly
--
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinf
Ok, this is all done.
One concern is in regards to the Hibernate Tools project. In Jira it
was linked to the JBoss FishEye server[1]. The last commit against
whatever repository that FishEye is indexing was ~2 months ago. The
hibernate-tools project under the hibernate GitHub organization[2]
I will work on getting the rest moved today. I really wanted to get
tools moved to this as it talks to the JBoss FishEye and can really
slow down all access to the JIra server as a whole.
I will also be removing the FishEye repo links.
On Fri 29 Jun 2012 08:04:10 AM CDT, Steve Ebersole wrote:
+1 ! Thanks Steve!
On 29 June 2012 10:34, Nicolas Helleringer
wrote:
> Very nice indeed
>
> Niko
>
> 2012/6/29 Hardy Ferentschik
>
>> +1 Looks very nice. I think we should enable it for the other projects as
>> well.
>>
>>
>> On Jun 29, 2012, at 4:48 AM, Strong Liu wrote:
>>
>> > seems open the
Very nice indeed
Niko
2012/6/29 Hardy Ferentschik
> +1 Looks very nice. I think we should enable it for the other projects as
> well.
>
>
> On Jun 29, 2012, at 4:48 AM, Strong Liu wrote:
>
> > seems open the change set in github is faster than fisheye, and more
> cleaner on github
> >
> > nice!
+1 Looks very nice. I think we should enable it for the other projects as well.
On Jun 29, 2012, at 4:48 AM, Strong Liu wrote:
> seems open the change set in github is faster than fisheye, and more cleaner
> on github
>
> nice!
>
> On Jun 29, 2012, at 2:42 AM, Steve Ebersole wrote:
>
>> Fin
seems open the change set in github is faster than fisheye, and more cleaner on
github
nice!
On Jun 29, 2012, at 2:42 AM, Steve Ebersole wrote:
> Finally got GitHub integration set up in Jira. Talking about the
> direct, built-in Jira support for GitHub, not talking to GitHub through
> FishE
Finally got GitHub integration set up in Jira. Talking about the
direct, built-in Jira support for GitHub, not talking to GitHub through
FishEye.
So far I have only enabled it on the ORM project (HHH). Take a look-see
and let me know what you think.
In HHH issues, you will see there are now
On the admin side it also gives you many more options over what gets
emailed (what kind of events) and to whom.
On Wed 23 May 2012 11:50:29 AM CDT, Emmanuel Bernard wrote:
> Email notifications are indeed much better and faster to open.
>
> On 23 mai 2012, at 12:39, Hardy Ferentschik wrote:
>
>>
Email notifications are indeed much better and faster to open.
On 23 mai 2012, at 12:39, Hardy Ferentschik wrote:
> Now that the upgrade hiccups are mostly sorted out I have to say I like the
> new version.
> The integration with fisheye is now much better and I especially like the new
> email
Now that the upgrade hiccups are mostly sorted out I have to say I like the new
version.
The integration with fisheye is now much better and I especially like the new
email notifications. Sweet!
--Hardy
On May 22, 2012, at 7:43 PM, Steve Ebersole wrote:
> I have received the updated plugin fr
I think we have FishEye integration working again. Let me know if you
see problems with FishEye intg.
We will have to see about GitHub connector later.
On Tue 22 May 2012 02:46:39 PM CDT, Steve Ebersole wrote:
> Ok, we got the JBoss plugin installed and re-enabled and everything
> with pull req
Ok, we got the JBoss plugin installed and re-enabled and everything
with pull request fields looked good to me.
There is a problem with it connecting to FishEye (Source tab) at the
moment. They are also investigating whether the GitHub connector might
work now after upgrading.
On Tue 22 May
I have received the updated plugin from JBoss and have passed it along
to Atlassian. They will need to restart the instance at some point for
it to be picked up.
After that we will see what we need to do to get the pull request fields
showing up again.
On 05/21/2012 05:50 PM, Steve Ebersole
49 ?
I m so sorry :s
Niko
2012/5/22 Steve Ebersole
> ok, i am going to disable the custom plugin for now...
>
>
>
> On Mon 21 May 2012 05:42:05 PM CDT, Sanne Grinovero wrote:
>
>> Nicolas,
>> it seems you opened 49 duplicate issues on HSEARCH; I can't blame you,
>> I guess you were clicking an
ok, i am going to disable the custom plugin for now...
On Mon 21 May 2012 05:42:05 PM CDT, Sanne Grinovero wrote:
> Nicolas,
> it seems you opened 49 duplicate issues on HSEARCH; I can't blame you,
> I guess you were clicking and debugging while attempting to create
> "HSEARCH-1131 Implement the
Nicolas,
it seems you opened 49 duplicate issues on HSEARCH; I can't blame you,
I guess you were clicking and debugging while attempting to create
"HSEARCH-1131 Implement the programatic API for @Spatial "
I tried to bulk-close them as duplicate, but the TOKENIZED problem
resulted me in blowing up
All of the remaining issues with the JIRA instance seem to be related
to that custom field. The custom field is used for associating pull
requests with the issue.
JBoss is planning the same upgrade, so they are planning on working on
getting that plugin upgraded. I spoke with the developer an
We even know what it means ;)
It's a constant from Lucene, most notably older JIRA was using this
very old Lucene version which still had the old name; looks like they
finally upgraded Lucene in JIRA 5, but the version of Lucene being
used now breaks the custom field type for pull requests.
Basical
Ah, ok.
On Mon 21 May 2012 09:29:02 AM CDT, Nicolas Helleringer wrote:
> Since this morning I am trying to create sub task to HSEARCH-923 and
> when I click More Actions=>Create Sub tasks it open a modal box.
> The create button of that dialog do an ajax call that I spied in
> Chrome integrated de
Since this morning I am trying to create sub task to HSEARCH-923 and when I
click More Actions=>Create Sub tasks it open a modal box.
The create button of that dialog do an ajax call that I spied in Chrome
integrated dev tools (should be the same with FireBug in FireFox).
I catched there the respon
Nicolas, where did you see this stack trace? When I try to create an
issue, it just sits on that create screen...
On 05/21/2012 08:46 AM, Nicolas Helleringer wrote:
> When I try to create a sub task issue I got the following :
>
>>>
>
> [image: Hibernate JIRA]
> Not Found (404)
> Could not
I even don't see there is a "Resolve" Button
On May 21, 2012, at 9:36 PM, Sanne Grinovero wrote:
> I can't resolve them :/
>
> Anybody able to click "resolve" on
> https://hibernate.onjira.com/browse/OGM-183 ?
>
> I just looked at permissions, and all seems right.. but I likely
> missed somet
When I try to create a sub task issue I got the following :
>>
[image: Hibernate JIRA]
Not Found (404)
Could not execute action
[QuickCreateIssue]:TOKENIZEDjava.lang.NoSuchFieldError:
TOKENIZED at
org.jboss.labs.jira.plugin.custfieldtypes.searchimpl.MultiURLCustomFieldIndexer.addDocumentFiel
On May 21, 2012, at 3:36 PM, Sanne Grinovero wrote:
> I can't resolve them :/
>
> Anybody able to click "resolve" on
> https://hibernate.onjira.com/browse/OGM-183 ?
not me :-(
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lis
I can't resolve them :/
Anybody able to click "resolve" on https://hibernate.onjira.com/browse/OGM-183 ?
I just looked at permissions, and all seems right.. but I likely
missed something.
On 21 May 2012 14:21, Steve Ebersole wrote:
> I do not experience a problem creating issues at all, so cann
I do not experience a problem creating issues at all, so cannot say.
On Mon 21 May 2012 03:19:25 AM CDT, Strong Liu wrote:
> yeah, just send out another email about this to the hibernate-all, and
> another big issue is I can't create new jira.
>
> On May 19, 2012, at 10:45 PM, Steve Ebersole wrote
yeah, just send out another email about this to the hibernate-all, and another
big issue is I can't create new jira.
On May 19, 2012, at 10:45 PM, Steve Ebersole wrote:
> They are still there as far as I can see. If you go to the direct URL
> you can see them. But there is something funky abo
They are still there as far as I can see. If you go to the direct URL
you can see them. But there is something funky about searches and
other bulk views of issues.
I have told Atlassian. We just have to wait to hear back.
On Sat 19 May 2012 07:36:46 AM CDT, Hardy Ferentschik wrote:
> Hi,
>
>
Hi,
what's up with https://hibernate.onjira.com?
There projects are there, but no issues? I think we were going to upgrade Jira
version, right?
Are we still in some sort of intermediate state or what is going on?
--Hardy
___
hibernate-dev mailing list
On 12/20/2011 02:55 PM, Sanne Grinovero wrote:
> I agree as well on interpreting "Closed" as "forever"; AFAIR new
> issues can be linked to the older closed ones so that while a comment
> might not be allowed, it's still possible to point to "follow ups" in
> case of need.
>
> I'm not sure however
On Dec 21, 2011, at 3:30 PM, Steve Ebersole wrote:
>> What is the problem with comments on closed issues? Some comments might even
>> be useful (aka "had the same problem, fixed now") However, if someone wants
>> to start a new discussion - tough luck. If the comment is legit we tell them
>> t
On 12/20/2011 01:18 PM, Hardy Ferentschik wrote:
> I agree with this as well. In HV and SEARCH we close the resolved issues
> after a release. While they are resolved they could be reopened and closed
> issues cannot be reopened again. A new issue should be created in this case.
>
> Closing the i
On 12/20/2011 11:40 AM, John Verhaeg wrote:
> On Dec 20, 2011, at 11:17 AM, Steve Ebersole wrote:
>
>> Which brings us to... do we really want to not allow Closed issues to be
>> reopened? I mean actually remove the transition? Or do we just want to
>> say that as a standard procedure we do not r
Comments below...
- Original Message -
> From: "Sanne Grinovero"
> To: "Hardy Ferentschik"
> Cc: hibernate-dev@lists.jboss.org
> Sent: Tuesday, December 20, 2011 12:55:38 PM
> Subject: Re: [hibernate-dev] JIRA issue status - Closed v. Resolved
&
I agree as well on interpreting "Closed" as "forever"; AFAIR new
issues can be linked to the older closed ones so that while a comment
might not be allowed, it's still possible to point to "follow ups" in
case of need.
I'm not sure however about enforcing this, but I'm not against it. I'd
prefer i
Hi
On Dec 20, 2011, at 18:17, Steve Ebersole wrote:
> According to Atlassian...
> * Resolved : A resolution has been taken, and it is awaiting
> verification by reporter. From here issues are either reopened, or are
> closed.
> * Closed : The issue is considered finished, the resolution is cor
1 - 100 of 135 matches
Mail list logo
