Hello,
I know this has been asked several times, but i couldn't find any solution to my problem.
I'm trying to test JMC for the company i work for, and i was able to set it up, after a lot of trials and errors (unfortunately i've found the documentation to be a bit sparse, and it covers only the "happy case").
Anyway, I am in the stage in which I can create issues from the JMC ios client, and i get them correctly in my JIRA instance, however, if i reply thru JIRA, the comment never makes its way to JMC on the phone.
The usual culprit is the
https://[OMISSIS]/jira/rest/jconnect/1.0/issue/updates?sinceMillis=1367844248962&uuid=[OMISSIS]&apikey=[OMISSIS]&project=[OMISSIS]
method, which gives different results than the (I gather) equivalent JQL query
project = "[OMISSIS]" and reporter = jiraconnectuser and uuid = "[OMISSIS]" and updated >= 1367844248962
Of course, from the JQL query I can correctly see the updated issues, that are absent from JCM.
If I GET that URL, I see this:
$ curl "https://[OMISSIS]/jira/rest/jconnect/1.0/issue/updates?sinceMillis=1367844248962&uuid=[OMISSIS]&apikey=[OMISSIS]&project=[OMISSIS]"
{"issuesWithComments":[],"sinceMillis":1367849522410,"crashReportingDisabledInJIRA":false}
$
I don't know why the sinceMillis in the reply is different than the one in the request, but I assue that's to be expected (it should be now()).
Since I have limited access to the server side, I can't look at logging there, except from that, I think that's all the data I can possibly gather to troubleshoot my problem.
What can cause an issue like this? The other answers I've seen were related to hosted JIRA services, but this is not my case.
What's the exact set of permission the jiraconnectuser needs in order for everthing to work correctly?
If this was a known and resolved issue, which in which version it was fixed?
Thanks,
Antonio
Community moderators have prevented the ability to post new answers.
Darren, unfortunately not.
My team and I decided it was definitely not worth our time conitnuing integrating JMC in our projects, considering the state of JMC itself and its support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.