tmszdmsk/jira4android

jira4android's Issues

Would this work with CyanogenMod jira?

I tried jira.cyanogenmod.org with https and http , with my username and password, and it just says "unknown host". I built the app myself, replacin Google Analytics with a dummy jar if that makes any difference. BTW my credentials are in the log.

Sub Domain Support?

It seems that the application doesn't support sub domains as an instance URL...

Enhancement: Allow to use "server filters" without selecting project first

The "server filters" feature does not depend on the selected project, AFAIU. They are global to user's account.
So I believe it's reasonable to allow the user go to filters immediately, without selecting a project.

More helpful about url format

Tried to connect to my jira-online account.

used

https://company.atlassian.net

and it just says wrong url format.

Something more helpful, for example an example would be nice.

Feature request: Implement background data sync for selected filters

It's frustrating to wait for the issue list to open each time I select a filter.
Would be nice if I could set an option to sync data in the background.

Sync enable/disable and the sync interval may be set globally in the application settings.
But the "Automatically sync this filter" checkbox should be done on a per-filter basis (e.g. when the filter is opened, hit the "Menu" button to access the filter options).

I think that the list of projects should also be synced, if the sync is globally enabled. It takes time to load it each time, too.

List of sub-issues should be displayed in parent issue

List of sub-issues should be displayed on the dashboard of the parent issue. Preferably on a separate "tab" , as the list may be long. Or just at the bottom of the "basic info" tab.

Support for JIRA urls with application context part and custom ports

Some jira instances are available under
https://hostname/application-context (e.g. https://example.com/jira).

Our application is adding :443 port number after what user inputs, so we end up with https://example.com/jira:443 - which is incorrect URL.

Fix that and think about jira instance urls with different than defualt ports (e.g. user inputs http://jira.example.com:8080)

Login to Jira using self signed ssl certificates

Trying to log in to a Jira with self signed ssl certificates via https gives a generic error "unknown host".
Could it be possible to make the app accept any ssl certificate or ask (popup) to accept a selft signed one?
Also a checkbox in the login page would be good.

Feature request: Allow opening issues in jira4android when clicking a corresponding URL system-wide

Scenario:

1. I login to a Jira instance in jira4android, and it registers URL handler for prefix https://hostname/suffix/browse/ which it knows to be the issue browser of the JIRA instance.
2. Later, I click an issue link (e.g. in browser or in an e-mail) which looks like https://hostname/suffix/browse/KEY-123
3. Standard system dialog pops up with an ability to open the link in a browser or in jira4android, with the ability to remember the choice.
4. If I choose jira4android in the dialog, it opens the issue dashboard for me in the application.

Similar functionality is implemented in the official Twitter app, for example.

Information about wrong login

When i want log in i have toast with information Unknown Error. I should see wrong username or password here is stack trace:

03-18 13:32:43.712: E/ProgressBarThread(909): Error:
03-18 13:32:43.712: E/ProgressBarThread(909): jira.For.Android.RemoteExceptions.RemoteAuthenticationException: SoapFault - faultcode: 'soapenv:Server.userException' faultstring: 'com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Invalid username or password.' faultactor: 'null' detail: org.kxml2.kdom.Node@44f10f48
03-18 13:32:43.712: W/System.err(909): com.jira4android.exceptions.AuthenticationException: jira.For.Android.RemoteExceptions.RemoteAuthenticationException: SoapFault - faultcode: 'soapenv:Server.userException' faultstring: 'com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Invalid username or password.' faultactor: 'null' detail: org.kxml2.kdom.Node@44f10f48
03-18 13:32:43.722: W/System.err(909): at com.jira4android.connectors.KSoapExecutor.handleRemoteExceptions(KSoapExecutor.java:92)
03-18 13:32:43.722: W/System.err(909): at com.jira4android.connectors.KSoapExecutor.execute(KSoapExecutor.java:59)
03-18 13:32:43.722: W/System.err(909): at com.jira4android.connectors.AuthenthicationService.login(AuthenthicationService.java:42)
03-18 13:32:43.722: W/System.err(909): at jira.For.Android.Connector.Connector.jiraLogin(Connector.java:185)
03-18 13:32:43.722: W/System.err(909): at jira.For.Android.Login.LoginThread.doInBackground(LoginThread.java:133)
03-18 13:32:43.722: W/System.err(909): at jira.For.Android.Login.LoginThread.doInBackground(LoginThread.java:1)
03-18 13:32:43.732: W/System.err(909): at android.os.AsyncTask$2.call(AsyncTask.java:185)
03-18 13:32:43.732: W/System.err(909): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
03-18 13:32:43.732: W/System.err(909): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
03-18 13:32:43.732: W/System.err(909): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1068)
03-18 13:32:43.732: W/System.err(909): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:561)
03-18 13:32:43.732: W/System.err(909): at java.lang.Thread.run(Thread.java:1096)
03-18 13:32:43.732: W/System.err(909): Caused by: jira.For.Android.RemoteExceptions.RemoteAuthenticationException: SoapFault - faultcode: 'soapenv:Server.userException' faultstring: 'com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Invalid username or password.' faultactor: 'null' detail: org.kxml2.kdom.Node@44f10f48
03-18 13:32:43.732: W/System.err(909): at com.jira4android.connectors.KSoapExecutor.throwJiraException(KSoapExecutor.java:110)
03-18 13:32:43.732: W/System.err(909): at com.jira4android.connectors.KSoapExecutor.handleRemoteExceptions(KSoapExecutor.java:88)
03-18 13:32:43.732: W/System.err(909): ... 11 more
03-18 13:32:43.742: W/System.err(909): Caused by: SoapFault - faultcode: 'soapenv:Server.userException' faultstring: 'com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Invalid username or password.' faultactor: 'null' detail: org.kxml2.kdom.Node@44f10f48
03-18 13:32:43.742: W/System.err(909): at org.ksoap2.serialization.SoapSerializationEnvelope.parseBody(SoapSerializationEnvelope.java:136)
03-18 13:32:43.742: W/System.err(909): at org.ksoap2.SoapEnvelope.parse(SoapEnvelope.java:137)
03-18 13:32:43.742: W/System.err(909): at org.ksoap2.transport.Transport.parseResponse(Transport.java:100)
03-18 13:32:43.742: W/System.err(909): at org.ksoap2.transport.HttpTransportSE.call(HttpTransportSE.java:195)
03-18 13:32:43.742: W/System.err(909): at org.ksoap2.transport.HttpTransportSE.call(HttpTransportSE.java:95)
03-18 13:32:43.742: W/System.err(909): at com.jira4android.connectors.KSoapExecutor.execute(KSoapExecutor.java:44)
03-18 13:32:43.742: W/System.err(909): ... 10 more