Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Cloud MacOS New App Error: "Mobile unable to get backlog for board 2" Edited

To have the Jira Cloud MacOS app now available on the store is amazing, however, I was disappointed with multiple issues which has resorted me back to the web based version.

Currently I have a empty project open, when clicking on the backlog tab I keep getting a error message "Mobile unable to get backlog for board 2" everytime.

Another issue, upon ignoring the error message, when i do manage to create an issue for the backlog, when I try to delete the item, its not automatically deleted so its still listed and when I try and delete it again i get a error message saying it has already been deleted but its still showing.

Has anyone else had this issue or can help me resolve it?

3 answers

0 votes

@dmaia92 I think I read this same comment in our internal feedback. 

We need to investigate what is happening. Would you mind sending us an email to jira-mobile@atlassian.com with the url that you are using in web to see your backlog?

We can then search on our logs what is happening.

Thanks

I have sent the email across, thank you! :) 

I am still getting same issue, I just ignore it but I hope it’s resolved soon after an update

For me this issue seem to be happening when backlog is empty

yes, you are right. It only happens when the backlog is empty. We have a ticket and we will address it soon. 

Just wanted to follow up on this ticket as I am having the same issue and wanted to see if there has been a fix/workaround identified

We are deploying the fix in our backends. Hopefully in the next 72 hours this issue will be mitigated.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

243 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you