It seems a user can add their time logged to any ticket, and this information is stored on the individual ticket.
We'd like to use this to track total hours for each user spent on certain types of tickets.
This will enable highly accurate time auditing for R&D grant purposes.
Is there an area where I can get a summary of the work logs, or is there an addon application that exists?
Cheers
Franco
Thank you for the update.
My database expert was able to find the user comment/solution you listed (https://confluence.atlassian.com/display/JIRA/JIRA+and+MS+SQL+Server+2008?focusedCommentId=264045977#comment-264045977). We did have to go through the process of creating a temporary login account in SQL Server in order to bypass the setup wizard and then update the configuration to use the NTLM authentication once we moved the login domain to the URL manually.
Though it's not your fault it works this way, this is an incredibly poor integration with one of Jira's 'production supported DBs'. Both on the technical level and on the documentation level. The NTLM authentication is a security industry best practice and should be addressed in the standard Jira installation documentation.
Do you know if there's a bug/feature request entered for this that I can 'vote' for, etc.
Thanks,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had the same error screen, but it turned out that postgresql was not starting.
Luckily postgres gave me the information I needed to know when I ran the "sudo service postgresql start" command in ubuntu.
In my case the failure was because of permissions on the postgresql install directory having been changed. Once I ran "chmod 700 the/address/of/postgres -R" and ran "sudo service postgresql start", "sudo service JIRA stop", and "sudo service JIRA stop" everything eventually came back online.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Caused by: java.sql.SQLException: Login failed for user 'ABNOLOGY\SVC_Jira'. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258) at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603) at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:357) at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
The user unable to login due to the following:
Caused by: javax.management.InstanceAlreadyExistsException: com.atlassian.jira:name=BasicDataSource at com.sun.jmx.mbeanserver.Repository.addMBean(Unknown Source) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(Unknown Source) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(Unknown Source)
Did your username password contained some special characters? If so you might hit into the bug addressed in this KB article: https://confluence.atlassian.com/display/JIRAKB/JIRA+Does+Not+Start+due+to+InstanceAlreadyExistsException
Try use a password without special character and see how it goes?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response, though the password only has letters and numbers mixed case.
I also checked the mutiple usertransaction defines and there's no conf/Catalina/localhost/jira.xml file to duplicate.
In server.xml, it contains:
-<Engine name="Catalina" defaultHost="localhost">-<Host name="localhost" unpackWARs="true" autoDeploy="true" appBase="webapps">-<Context useHttpOnly="true" reloadable="false" path="" docBase="${catalina.home}/atlassian-jira">
<!-- ==================================================================================== Note, you no longer configure your database driver or connection parameters here. These are configured through the UI during application setup. ==================================================================================== -->
<Resource name="UserTransaction" type="javax.transaction.UserTransaction" jotm.timeout="60" factory="org.objectweb.jotm.UserTransactionFactory" auth="Container"/><Manager pathname=""/></Context></Host>
Any other thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
since you using NTLM authentication, try the suggestion to add the domain to the jdbc URL and use the username(without the domain) as suggested by the user comment over here: https://confluence.atlassian.com/display/JIRA/JIRA+and+MS+SQL+Server+2008?focusedCommentId=264045977#comment-264045977
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.