Push Notifications are a popular feature of the Mobility for Jira apps. Push Notifications are sent to by your Jira Server/Cloud instance upon changes to issues. To enable notifications please do the following on your device:
Team Apps: Profile > Settings > Notifications then select the Jira event you are interested in
Portal Apps: Profile > Settings > Push Notifications turn on the switch
Once a user enabled notifications, they will start receiving push notifications if they are
Enabled the specific Jira event (Team only, Portal will receive all events)
If you are having issues receiving any Push Notifications, please check the following points below:
Make sure you have the latest Mobility for Jira add-on version installed (certificates expire over time)
Ensure that Push Notifications are enabled for both iOS and Android (Jira Administration > Manage Apps > Mobility for Jira > Configuration)
When starting up Mobility for Jira Team for the first time
a. Accept to receive push notifications when you first start the app
b. Ensure that Push Notifications are enabled under Profile in the app
In Jira Server go to Administration > Manage Apps > Mobility for Jira > Devices
a. Is your device registered and all all the events turn on?
b. Try to remove all entries and re-register your device with the steps above
When you test notifications, make sure your user is the reporter, assignee, or watcher of the issue you are testing with. Make sure you use a different user account to make a change to your test issue since you won't receive changes that you make yourself
Check your Jira Server firewall settings:
a. Push Notifications are sent from your Jira server to the Apple APN Gateway to be delivered the devices. Please make sure your Jira server can send out TCP packets to gateway.push.apple.com on port 2195 and that they aren’t blocked by your firewall.
b. For Android devices, the Firebase Cloud Messaging (FCM) service is used. Your Jira server needs to be able to make outbound calls on ports 5228, 5229, and 5230. GCM typically only uses 5228, but it sometimes uses 5229 and 5230. GCM doesn’t provide specific IPs.
There are some known issue with H2 (in-memory database), usually only used for testing but not production.
Here is additional information: