nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Cloud App teams doesn't work if the ticket description is too big

fegbers

Hello all,

Does anyone know if there is a maximum size of a ticket that can be forwarded to teams? We are missing some ticket notifications to teams with a large description...

Otherwise, is there any way to replace the message to teams with an appropriate message, e.g. "The text is too large, please open the link to the ticket to see the text"?

Thanks for the help!

Accepted answers

fegbers

If anyone is interested in a response from the support team (the final response & shortened):

Hello Finn,

Thank you so much for giving me time to investigate this, below are my findings

Test #1 -

I sent a post from Jira issue to an external webhook with a huge set of data in the description. Payload was received

Test #2

I sent a post from Jira issue with the same set of data to MS teams webhooks and this was not received

I sent the same data from Postman to MS teams and the data was not received on teams.

I verified the configuration is valid by sending a small set of data and the test was successful for teams on both thee above methods. So we can conclude teams is not happy with large sets of data.

Upon investigating this further we can see that the MS team's webhook connector is sending the below response.

Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 413 with ContextId MS-CV=Bf6EuXgJwUe0E5cNeRQF1A.0..

It is documented from Microsoft that there is a limitation with MSteams incoming webhook connector as stated below

The message size limit is 28 KB. When the size exceeds 28 KB, you receive an error. For more information, see Limits and specifications for Microsoft Teams.

Source: Create Incoming Webhooks MS Teams

Unfortunately, This connector is owned by Microsoft and we do not have control over it, However, I tested this with the official Jira connector on teams, and it works as expected because if the description is huge the data is only previewed.

Link: Channel notification MS teams

I hope the above information was helpful

With that said, I will move the case to Suggested Resolution so you can accept it if everything goes well at your end.

However, If you still have any additional questions about it, simply comment on this case and I will be more than happy to assist you.

Kindly note that following three days of inactivity on this thread, this ticket would automatically be marked as solved.

All comments

Christopher Maxwell

Hi Finn,

Jira Cloud Description maximum length is 255 characters. Single line text field supports 254 characters.

For Body, I found API reference to 50,000 characters, yet there is a character limit of the Description field which is actually 32,767 (I just confirmed/tested that).

I found a feature request for Jira Cloud that is requesting description and comment fields to have unlimited text:

https://jira.atlassian.com/browse/JRACLOUD-59124

If you would find that feature help you can vote for, and watch, the feature request.

However, your issue sounds primarily like an issue with forwarding tickets.

To help me better understand your context:

How are you forwarding tickets?

and, would you upload a screenshot showing a problematic notification?

Have a great week!
Christopher

fegbers

Hi Christopher,

I think there is a misunderstanding. The Ticket was created successfully and should be forwarded to Microsoft Teams via the issue notifications and Jira Cloud App Teams. But this was not the case..

I just wrote with atlassian support. Maybe they can forward the problem and create an issue / feature request.

I will keep this thread up to date.

Greetings

Christopher Maxwell

Hi Finn,

Yes, then, this sounds like a notification issue. If regular issues are notifying, and similar issues with long descriptions are not, and if the long descriptions are within the accepted character limits ---- you were spot on to reach out to Atlassian Support. They are phenomenal and should be able to get your issue resolved.

Thank you for posting updates here!

Have a great week,
Christopher

fegbers

As promised the support answer if anybody else has a similar issue: https://support.atlassian.com/requests/JST-855543/

fegbers

If anyone is interested in a response from the support team (the final response & shortened):

Hello Finn,

Thank you so much for giving me time to investigate this, below are my findings

Test #1 -

I sent a post from Jira issue to an external webhook with a huge set of data in the description. Payload was received

Test #2

I sent a post from Jira issue with the same set of data to MS teams webhooks and this was not received

I sent the same data from Postman to MS teams and the data was not received on teams.

I verified the configuration is valid by sending a small set of data and the test was successful for teams on both thee above methods. So we can conclude teams is not happy with large sets of data.

Upon investigating this further we can see that the MS team's webhook connector is sending the below response.

Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 413 with ContextId MS-CV=Bf6EuXgJwUe0E5cNeRQF1A.0..

It is documented from Microsoft that there is a limitation with MSteams incoming webhook connector as stated below

The message size limit is 28 KB. When the size exceeds 28 KB, you receive an error. For more information, see Limits and specifications for Microsoft Teams.

Source: Create Incoming Webhooks MS Teams

Link: Channel notification MS teams

I hope the above information was helpful

With that said, I will move the case to Suggested Resolution so you can accept it if everything goes well at your end.

However, If you still have any additional questions about it, simply comment on this case and I will be more than happy to assist you.

Kindly note that following three days of inactivity on this thread, this ticket would automatically be marked as solved.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud