Thanks for everyone's feedback, JIRA 5.1 was released today.

https://confluence.atlassian.com/display/JIRA/JIRA+5.1+Release+Notes

Yup, well spotted, I had a bunch of spring dependencies, though I them with provided scope, so I would have thought they would not have caused a problem, well, all except spring-ldap-core... tnx

javahollic - I've tried to replicate your problem, but am unable to. It looks to be a Spring version conflict from the limited info in the stack trace - maybe you have a dependency on Spring (maybe even transitively) in your plugin?

I use AO, but my plugin, whilst compiling fine is failing to deploy on install due to the following, advice?

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'tx-processor' defined in URL [bundle://94.0:0/META-INF/spring/atlassian-plugins-components.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [com.atlassian.activeobjects.external.ActiveObjects]: : Error creating bean with name 'ao': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalArgumentException: interface org.springframework.aop.IntroductionInfo is not visible from class loader; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ao': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalArgumentException: interface org.springframework.aop.IntroductionInfo is not visible from class loader
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:591)
	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:193)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
	at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:880)
	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.registerBeanPostProcessors(AbstractDelegatedExecutionApplicationContext.java:551)
	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.registerBeanPostProcessors(AbstractDelegatedExecutionApplicationContext.java:486)
	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:336)
	at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
	at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
	at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

Is AO fully validated in RC3? I'm depending on 0.9.17 which is shipped with RC3 and I'm not depending on IntroductionInfo...

Bryan - yes, thank you. It's an issue getting JIRA 5.0.6 with GH 5.10.3 - so I got redirected here by mistake (they thought I was using JIRA 5.10.3). Following up on the GHS bug.

Malachi, thanks for letting us know. This EAP Feedback issue covers feedback on the JIRA 5.1 Early Access Program release (not bug fix releases like JIRA 5.0.6). The GreenHopper issue you mentioned is a story about sprint reports. Did you mean to include the issue key for a GreenHopper bug? If there's an issue with GreenHopper on a current release of JIRA, definitely file a bug against GreenHopper so we can look into it. (Or let us know if you meant something else entirely.)

I just created JRA-28625.
Looking at my profile on http://jira.atlassian.com I noticed that the Summary on an issue in my activity feed did not match the issue.

Stephan, thanks for the feedback. Unless the user is logged into your JIRA instance (i.e. has an active session), they will not see the link to the issue on your JIRA instance. I.e anonymous users don't see the link, they just see the thank you message. Is there anything else that you would want to edit in the template that you can't edit in the custom template today?

The issue collector is great, but it's very important that all templates can be edited. For example: If I use this feature on a public website the user shouldn't know which Issue was created and how the link to my issue server.

I retested the with your scenarios. I tested with Description only before and you did reproduce my issue of two enter keys loses the description text. You called it clear. I did not say it saved but the only way to recover is to either reload the page or cancel to get your old text back.

I tested with summary field and got the same behavior as yours. The edit box does not close on enter.

In the case of components, I would say nothing is selected and hitting the enter does nothing since the edit box stays open. (Which is good!) It could be saving, but I do not have any feedback to that effect while editing. I am not hooked up for email on my test system, so I do not know if an email is generated or not.

,c<enter><enter>

On the summary field summary field though I tried a different test, if I typed
,s<enter><space><click on save icon>
then the field tries to save but never completes. I would have expected an error message since the summmary field is required or it should have completed since a space replaced whatever text was in the summary field.

nabramovitz
It is normally safe to upgrade such plugins, but still I would not normally recommend upgrading system plugins in a production environment.
It is absolutely fine for you to install other plugins.

Note that UPM, Atlassian Bot Session Killer, and FishEye Plugin will all be upgraded in the next EAP release of JIRA.

Thanks for your feedback Norman.

To clarify, the new "comma operator" functionality should not ever land you in a situation where consecutive enter keys will clear and save values.

• For single text field like Summary: Enter will just re-save what you had - even if all the text is highlighted.
• For selections like Component: Enter will just re-save what you had too.
• For text area fields like Description: Enter will "clear" your text selection for a new line, but subsequent Enter's will continue to produce new lines - not save. You can only save when you tab to the tick, or if you hit the "save" shortcut key.

Is this contrary to what you are seeing, if so, can you tell us what you've done step by step?

I like the idea of the comma operator, but it does concern me that the text gets highlighted and the last character I typed was an enter key. If I accidentally, hit the enter key twice, I would lose my text.

I loaded up m3 release and I going to try to install the subversion plugin and I was surprised by seeing that the upm, Atlassian Bot Session Killer, and FishEye Plugin were out of date. Is ok to upgrade these plugins and attempt to install other plugins?

It is a good base to build a more enterprise mechanism, but the current mechanism is based upon trust that the commenter knows when to change the security level. It also only allows one role or group to be selected as far as I can tell. I will put my thoughts together and either create an issue or attempt or use this as a basis to learn about plugin writing.

@Norman, Comment Security Levels sounds like exactly what you're looking for.
Look at:
Configuring JIRA Options, in the "Comment visibility" option.
And to see how this works in practice:
Commenting on an Issue

Maybe I am confused or maybe our setup is not using permissions/groups correctly, but if a person creates an issue he gets to see everything written because he created the issue(jira_user group). The creator may not be able to move things through the transitions, but he can see all the comments. When a developer adds a comment, I never saw a way to state only developers can see that comment. We are not trying to block users from seeing the progress, but we want to make sure the comment's language is appropriate. If 'private/restricted' comments exists, please point me in the right direction and I can experiment on the new EAP release.

We solve this issue by making our project leaders responsible to review their project's comments and have their people correct them. After a very short while the developers are aware to use appropriate language and the issue goes away. :>)

JIRA 5.1 EAP 2 (m3) is now available for download. Check out the release notes here.

Thanks in advance (from the entire JIRA team) for your feedback!

Norman, thanks for both of your comments.

For the autowatch changes, I understand that users would see notifications if they created the issue, and that's an important change in behavior. We will make sure this is heavily documented in the final release notes for 5.1. You mentioned that the creator of the issue would see information they normally could not see - we don't send information to users unless they have permission to see it on the issue. I.e. comments which have a comment security level set only go out users who can see those comments on the issue. Let me know if I'm missing something else here?

For the inconsistent ads, thanks for noting it. I'll raise a bug so we investigate it.

I am getting inconsistencies when your ads for crucible and fisheye display. When I created an dummy issue and clicked on the all tab no ads are displayed. If I use the browser's refresh button the ads appear.

In some cases if I click the all tab and the ads appear and then I click the review tab and then click back to the all tab. the ads do not appear. When I was on the review tab, I had the waiting icon, but I did not wait for it to complete.

In some cases when I ads appear on the all tab and I click the review tab. I get the waiting icon but does not seem to complete evan after 60 seconds.

I am usng your in-memory database on version (v5.1-m2#757-sha1:32c7a68) on IE8 using Windows xp sp3

You can also try adding a comment after creating an issue before clicking on the all tab.

I am assuming this where I should enter comments about the 5.1 EAP. Please consider not enabling autowatching by default. With a complex workflow that contains multiple steps(,research, qa, integration, pre-release, released) that interfaces across multiple groups and with the ability for outside users creating issues, the creator of the issue may be getting information that may not be appropriate for them to see. Imagine some developer chatter getting out talking about customers.

You are currently making it more difficult to disable this autowatch feature since it on a per user basis and I did not see way to disable/enable from the admin panel.

Please consider adding an item to the general system adminstration panel to enable/disable autowatching instead. (Which is different from capability of watching which you have now.)

Also please consider adding a BIG warning that can be put in the release/upgrade guides about what the ramifications of turning on autowatching means for an organization.

Thanks for letting us know, Andrey. Preparing for JIRA 5.1 should be accessible now!

Cool. But page https://developer.atlassian.com/display/JIRADEV/Preparing+for+JIRA+5.1 is inaccessible

The first EAP is now available for download.

mou, you're right and that's because we're preparing our all resources (such as this one) for next weeks release. Thanks for keeping a keen eye on us!

There are no downloads behind the specified link.