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.

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)

If anyone would like to provide feedback on changes to the WFD, please see: JRA-33692

I tried to start my plugin JIRA Project Role Tab with m04 with test data and got the following "license too old" error message

localhost-startStop-1 ERROR      [atlassian.jira.license.LicenseJohnsonEventRaiserImpl] The current license is too old (14/Mai/13) to run this version (6.2-m04 - Tue Nov 19 00:00:00 CET 2013) of JIRA.
localhost-startStop-1 ERROR      [atlassian.jira.upgrade.UpgradeLauncher] No upgrade is being performed due to detected inconsistencies. The current license is too old to install this version of JIRA (6.2-m04)

Any idea, what's going on? My plugin does not require a license. It seams, that some JIRA internal stuff is requiring a new one?

For the new auditing feature, I see from the m4 release notes that the current list of things recorded is

user added, updated or deleted
group added, updated or deleted
permission added ore removed from permission scheme
permission scheme created, updated or deleted
workflow created, updated or deleted
audit system enabled or disabled

Other questions and the actions that I recall looking up in recent years with the JIRA Auditor plugin are:

User name/id changed (that may be "user updated" above)

Group membership changed (that may be "group updated" above)

Screen, Screen Scheme, Issue Type Screen Scheme - updated. "Who made that field appear in my screen?"

Custom Field added, updated. "Who added all these new custom fields?"

Field Configuration, Field Configuration Scheme - updated. "Who made this field required?"

then lower priority:

Status, Resolution, Issue Types add, updated, deleted - "what is this new issue type, who can I ask about it?"

Indexing - who started that last reindex and how long did it take?

Permissions Schemes, Issue Security Schemes,

Overall I think that deciding what to audit is often best decided by coming up with the questions that JIRA administrators ask, e.g. the great "where's my field" functionality that was added a few versions ago

I added a link to JRA-36513 about not being able to distinguish different sub-task's statuses that have the same color (category)

how is this program going? do many folks try the EAP downloads and provide feedback? How do the EAP bits compare with the OD bits? I.e will 6.2-OD4 be on-par with 6.2-m4?