1 1- IP Allowlist
2 2- Functional Limitations
3 3- Capacity Limitations
- 3.1 4 September 2023
  - 3.1.1 DEPRECATION NOTICE Introducing per issue limits for issue list fields

1- IP Allowlist

When your Jira instance uses the IP Allowlist to limit access to Jira, please make sure you allow access for the Forge Platform as well.
If the correct IP ranges are not included, our Forge app will display the following message:

All our Forge apps are hosted on the Atlassian Forge platform. The required IP ranges should be retrieved from the Atlassian documentation, which can be found here:

IP addresses and domains for Atlassian cloud products | Atlassian Support
https://ip-ranges.atlassian.com/ (product = forge)

13.52.5.96/28
13.200.41.224/28
13.236.8.224/28
15.229.145.224/28
16.63.53.224/28
18.136.214.96/28
18.184.99.224/28
18.234.32.224/28
18.246.31.224/28
43.202.69.96/28
52.215.192.224/28
104.192.136.240/28
104.192.137.240/28
104.192.138.240/28
104.192.140.240/28
104.192.142.240/28
104.192.143.240/28
185.166.140.112/28
185.166.141.112/28
185.166.142.240/28
185.166.143.240/28
18.236.52.165/32
34.215.254.205/32
35.160.6.102/32
52.43.192.52/32
52.89.100.78/32
54.190.195.254/32
54.214.155.219/32
54.218.196.28/32
52.195.248.93/32
54.65.219.119/32
43.207.238.123/32
3.114.146.111/32
54.248.180.178/32
57.180.171.119/32
3.37.121.177/32
3.34.165.169/32
15.164.153.22/32
43.201.237.75/32
13.209.252.121/32
15.165.21.19/32
43.202.223.238/32
3.34.8.241/32
15.206.230.70/32
3.7.242.212/32
43.205.183.186/32
13.200.51.21/32
13.200.127.18/32
65.2.173.31/32
18.142.175.136/32
54.254.13.217/32
52.220.108.50/32
54.255.41.156/32
52.77.196.9/32
18.143.11.169/32
52.65.164.184/32
13.237.143.132/32
3.105.255.118/32
3.104.191.162/32
13.238.244.22/32
3.106.172.84/32
15.156.32.59/32
15.222.164.249/32
15.156.255.184/32
3.98.151.27/32
3.96.73.34/32
35.182.178.44/32
18.196.69.189/32
52.58.86.18/32
3.77.185.155/32
18.153.162.220/32
3.126.237.94/32
18.157.151.173/32
16.63.192.113/32
16.63.86.27/32
16.63.153.19/32
16.63.156.232/32
16.63.10.60/32
16.63.133.73/32
54.76.137.153/32
34.253.103.242/32
63.34.104.55/32
54.220.63.40/32
54.154.186.82/32
52.208.56.204/32
13.43.230.20/32
13.42.94.26/32
13.41.178.119/32
13.43.10.138/32
18.132.72.151/32
13.43.238.10/32
54.94.144.45/32
15.229.167.123/32
177.71.171.149/32
18.229.170.213/32
54.232.43.18/32
52.67.212.82/32
3.220.210.28/32
34.231.161.126/32
34.194.73.28/32
3.231.15.71/32
3.224.137.93/32
52.55.61.132/32
54.156.218.101/32
34.194.247.143/32
52.53.140.163/32
54.193.160.145/32
54.241.128.19/32
13.56.84.222/32

2- Functional Limitations

The Jira Forge platform has some limitations, addressed to Atlassian:

Custom Fields in Transition Screens: Forge currently lacks support for adding custom fields to workflow transition screens (Issue Pickers..).
Service Management Integration: There are limitations in supporting some functionalities in Jira Service Management, like adding the Issue Picker custom fields to the portal.
Data Residency: Forge apps do not currently support data residency options, meaning all data is handled through US-based AWS infrastructure. This can be a significant limitation for compliance with data privacy regulations like GDPR (Atlassian Developer) (The Atlassian Developer Community). See: https://developer.atlassian.com/platform/forge/data-residency/#:~:text=In%20line%20with%20this%2C%20we,to%20an%20admin
UI Modifications not supported for Transition Screens
Internationalization: There is no support for internationalization, making it challenging to develop apps that need to cater to multiple languages and locales (Atlassian Developer).
Private Marketplace Listing: Forge does not support private marketplace listings, limiting the ability to distribute apps privately within specific organizations or groups (Atlassian Developer).

3- Capacity Limitations

Please refer to the capacity limitations enforced by Atlassian:: https://developer.atlassian.com/changelog/#CHANGE-1133

4 September 2023

DEPRECATION NOTICE Introducing per issue limits for issue list fields

REST API - Jira Cloud Platform

REST API - JSM Cloud

REST API - Jira Software Cloud

In 6 months, we will enforce limits per issue for the number of:

Comments: 5000 comments per issue
Worklogs: 5000 worklogs per issue
Attachments: 2000 attachments per issue
Issue links: 2000 issue links per issue (excluding child issues and subtasks)
Remote links: 2000 remote issue links per issue

An error response will occur if the limit is exceeded for:

Operations via REST APIs
Automation rules
Issue transitions

There will be no change for existing issue data that is already over the limit. All existing issues over the limit will be retained as is.

VIP.LEAN DOCU

Atlassian Forge Platform Limitations

1- IP Allowlist

2- Functional Limitations

3- Capacity Limitations

4 September 2023

DEPRECATION NOTICE Introducing per issue limits for issue list fields