-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
0
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Thanks for trying out our early look at our next release. You can download the latest EAP release (milestone build, beta or release candidate) here.
Please read through Preparing for JIRA 6.2 if you are a plugin developer.
We really appreciate you taking the time to provide us any feedback on the contents of the EAP.
Simply comment below for any comments you may have.
- has a derivative of
-
JRASERVER-37105 NPE when adding an smtp mail server
-
- Closed
-
- relates to
-
-
- Closed
-
-
JRASERVER-36401
Dashboard gadgets fail to render after upgrading from 5.2.5 to 6.2 (m03)
-
- Closed
-
-
JRASERVER-37007
Data Base error upgrading from 6.1.5 or 6.1.7 (Test box)
-
- Closed
-
-
- Closed
-
JDEV-27075 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
[JRASERVER-35317] EAP Feedback - JIRA 6.2
For the Audit Log I would like to see Role added. It tells me when A Role is deleted but not when one is added. Seems odd that it is only one way.
For the auditing, is CSV the only format available for export? Any plans for other formats?
JIRA (v6.2-rc1#6252-sha1:c8fda5e) , with no mail servers configured, adding one results in a NPE in a comparator
java.lang.NullPointerException java.lang.NullPointerException at com.atlassian.jira.plugins.mail.webwork.AddSmtpMailServer$1.compare(AddSmtpMailServer.java:46) at com.atlassian.jira.plugins.mail.webwork.AddSmtpMailServer$1.compare(AddSmtpMailServer.java:42) at java.util.TreeMap.put(TreeMap.java:530) at java.util.TreeSet.add(TreeSet.java:238) at java.util.AbstractCollection.addAll(AbstractCollection.java:305) at java.util.TreeSet.addAll(TreeSet.java:295) at com.atlassian.jira.plugins.mail.webwork.AddSmtpMailServer.doDefault(AddSmtpMailServer.java:52)
I keep running in to the following error trying to push in the data from our production system to test.
System Ubuntu 12.04LTS VM
2GB Ram
psql database
Error:
2014-01-29 15:37:41,920 JiraImportTaskExecutionThread-1 ERROR Admin 925x192x1 17id0gl 127.0.0.1 /secure/admin/XmlRestore.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: java.lang.RuntimeException: com.opensymphony.workflow.FactoryException: Error converting XML to workflow descriptor.: root cause: Attribute "name" is required and must be specified for element type "action". (line:425 col:26)
How I have tried to get this to run.
On our Sandbox server i tried an upgrade and it failed with the same error. On my VM i tried to import during setup then fully setup jira and tried to restore.
Update: on the 6.2 Beta I am getting the same error trying to push in the data.
Feedback from Mike Girgis on the Auditing documentation (see comment):
"All events relating to shared objects should be audited. All events relating to add-ons should be audited."
Hey martin.brueggemann!
Thanks for your comment. I agree, there is a lot of LDAP synchronisation events that are there and I agree it may be difficult to see the other events in there. In upcoming EAP and OD releases we will fix that by ignoring some of the events which we found to be of little value, but also by providing you with filtering capabilities embedded into GUI. Stay tuned.
Re Bartek and Matt:
In its current setup, the auditing table contains a lot of white noise.
IMHO it's a must to be able to at least sort the table - better: to filter out event levels or sources.
(as is done in every IDE, where I can tell the compiler to only show warning and errors)
Hi matt.doar,
Thanks for your comments. The list of recommended events to take a stab at next will be very helpful for us in the prioritisation effort.
Mind that the following events from your recommendations are already monitored:
- user name and full name change plus user creation and deletion
- change group membership changes (users being added or removed from a group) plus group creation and deletion
- permission and permission scheme creation, deletion and change (also including global permissions)
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center