infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafael Weingärtner (JIRA) <j...@apache.org>
Subject [jira] [Updated] (INFRA-16006) Jira showing The entered text is too long
Date Tue, 13 Feb 2018 23:43:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rafael Weingärtner updated INFRA-16006:
---------------------------------------
    Description: 
Hello Infra team, 
I am trying to edit the description on https://issues.apache.org/jira/browse/CLOUDSTACK-10169,
but so far I have not had success. I keep getting an error message "The entered text is too
long. It exceeds the allowed limit of 32,767 characters". 

I tried then removing some characters, but still without success. It seems that this might
be caused by last Jira updates. can you take a look into it?

  was:
Hello Infra team, 
I am trying to edit the description on https://issues.apache.org/jira/browse/CLOUDSTACK-10169,
but so war I have not had success. I keep getting an error message "The entered text is too
long. It exceeds the allowed limit of 32,767 characters". 

I tried then removing some characters, but still without success. It seems that this might
be caused by last Jira updates. can you take a look into it?


> Jira showing The entered text is too long
> -----------------------------------------
>
>                 Key: INFRA-16006
>                 URL: https://issues.apache.org/jira/browse/INFRA-16006
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA
>            Reporter: Rafael Weingärtner
>            Priority: Major
>
> Hello Infra team, 
> I am trying to edit the description on https://issues.apache.org/jira/browse/CLOUDSTACK-10169,
but so far I have not had success. I keep getting an error message "The entered text is too
long. It exceeds the allowed limit of 32,767 characters". 
> I tried then removing some characters, but still without success. It seems that this
might be caused by last Jira updates. can you take a look into it?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message