Comments entered in response to user feedback are not displayed on the iPhone

Eduardo Oliveira July 13, 2012

This is a problem which has been reported in other questions before and I tried the answers without success. When a user sends feedback via Jira Mobile Connect, the feedback shows up on Jira OnDemand but the comments entered in response to the feedback are not delivered back to the user on the iPhone.

I already tried going into Administration -> System -> Indexing and asking for a re-index (3 times) and that didn't help.

This is the information displayed on the debug output on the emulator:

2012-07-13 17:07:22.587 [81427:207] 121 -[CrashReporter init] Crash reporter enabled.
2012-07-13 17:07:22.589 [81427:207] 322 -[JMC start] JIRA Mobile Connect is configured with url: https://(ommited).atlassian.net/
2012-07-13 17:07:24.627 [81427:207] 55 -[JMCPing sendPing] Retrieving notifications via: https://(ommited).atlassian.net/rest/jconnect/1.0/issue/updates?sinceMillis=0&uuid=(ommited)&apikey=(ommited)&project=(ommited)
2012-07-13 17:07:25.118 [81427:207] 73 -[JMCPing didReceiveComments:] Time JIRA last saw this user: 2012-07-14 00:07:25 +0000
2012-07-13 17:07:25.119 [81427:207] 113 -[JMCPing connectionDidFinishLoading:] Flushing the request queue
2012-07-13 17:07:25.120 [81427:207] 61 +[JMCRequestQueue sharedInstance] queue at (ommited)

The URL contacted by the JMC replies with just the following:

{
sinceMillis: 1342224981475,
crashReportingDisabledInJIRA: false,
issuesWithComments: [ ]
}

As if there was no data to deliver.

And these are the options we're using:

// configure the JIRA Connect module for user feedback
JMCOptions *options = [JMCOptions optionsWithUrl:@"https://(omitted).atlassian.net/"
projectKey:@"(omitted)"
apiKey:@"(omitted)"
photos:TRUE
voice:TRUE
location:FALSE
crashReporting:TRUE
notifications:TRUE
customFields:NULL];

[[JMC sharedInstance] configureWithOptions:options];

Since there are no errors on the debug output and the JMCPing retrieves an empty set of comments, is it safe to assume that this problem is on the Jira servers instead of on the iPhone client?

Anything else to try other than requesting a re-index?

I'm happy to provide more details.

1 answer

1 accepted

0 votes
Answer accepted
Eduardo Oliveira July 16, 2012

Somehow it started to work -- without any further client changes.

So I can only guess it was a problem with Jira OnDemand which fixed itself.

Suggest an answer

Log in or Sign up to answer