-
Bug
-
Resolution: Fixed
-
Low
-
10.111.3
-
1
-
Severity 3 - Minor
-
No
Issue Summary
The feature summary field allows users to enter more than 255 characters in Jira Align but Jira allows only 255.
When synchronising the feature created in Jira Align to Jira, the API will give the error "summary: Summary must be less than 255 characters.", and the feature will not be pushed to Jira as a result.
Steps to Reproduce
- Create a Feature for a program associated with a Jira Project
- Add to the description and summary a text with more than 255 a mix of accented and non characters such as:
Sed ut perspiciatis unde omnis iste natus error sît voluptatem accusantium doloremque laudantium, totam rm aperiam, eaque ipsa quaé ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quià voluptas sit aspernatur aut odit aut fugit, sed quia
- Select the 'Jira Project' accordingly from the drop-down field.
- Click on the 'Save' button
-> No error
Expected Results
Similar to the validation logic on the Feature name, the field should not allow users to enter more than 255 characters.
Actual Results
No error is given to the user. The text may be truncated but if not once the Jira Connector tries to create the issue in Jira, the error below is thrown:
{
Exception: AgileCraft.Jira.Api.Model.JiraApiException: summary: Summary must be less than 255 characters.
at AgileCraft.Jira.Api.JiraManager.ExecuteWithResponse[T](RestRequest request, String jiraApiResource, HttpStatusCode expectedHttpStatusCode, Boolean forceResponseLogging, Boolean& sessionAuthenticationExpiration, Boolean throwExceptionOnError, Boolean ignoreLogoutResponse, Boolean hideRequestBody, String[] queryParametersToHashForLogging) in C:\projects\alignintegration\AgileCraft.Jira.Api\JiraManager.cs:line 2214
at AgileCraft.Jira.Api.JiraManager.CreateEpic(CreateEpic newIssue, Int32 FeatureID, String projectKey) in C:\projects\alignintegration\AgileCraft.Jira.Api\JiraManager.cs:line 1055
at AgileCraft_Jira.AgileCraft.CreateFeatureInJira(JiraManager manager, DataRow row2, Boolean multipleFeature) in C:\projects\alignintegration\Connectors\JiraServiceProduction\AgileCraft_Jira\AgileCraft.cs:line 5980
Level: Error
MessageTemplate: CreateFeatureInJira:Failed to create Jira issue for Feature
Properties: { [-]
Action: IssuePushToJira
Build: 10.111.2.20578
ConnectorId: 1
CorrelationId: 1213256311
Customer: <Customer>
Event: ContinuousTimer
ExceptionDetail: { [-]
HResult: -2146233088
Message: summary: Summary must be less than 255 characters.
Source: AgileCraft.Jira.Api
StackTrace: at AgileCraft.Jira.Api.JiraManager.ExecuteWithResponse[T](RestRequest request, String jiraApiResource, HttpStatusCode expectedHttpStatusCode, Boolean forceResponseLogging, Boolean& sessionAuthenticationExpiration, Boolean throwExceptionOnError, Boolean ignoreLogoutResponse, Boolean hideRequestBody, String[] queryParametersToHashForLogging) in C:\projects\alignintegration\AgileCraft.Jira.Api\JiraManager.cs:line 2214
at AgileCraft.Jira.Api.JiraManager.CreateEpic(CreateEpic newIssue, Int32 FeatureID, String projectKey) in C:\projects\alignintegration\AgileCraft.Jira.Api\JiraManager.cs:line 1055
at AgileCraft_Jira.AgileCraft.CreateFeatureInJira(JiraManager manager, DataRow row2, Boolean multipleFeature) in C:\projects\alignintegration\Connectors\JiraServiceProduction\AgileCraft_Jira\AgileCraft.cs:line 5980
TargetSite: RestSharp.IRestResponse`1[T] ExecuteWithResponse[T](RestSharp.RestRequest, System.String, System.Net.HttpStatusCode, Boolean, Boolean ByRef, Boolean, Boolean, Boolean, System.String[])
Type: AgileCraft.Jira.Api.Model.JiraApiException
}
FeatureId: <FeatureId>
JiraProjectKey: <ProjectKey>
JiraProjectKeys: [ [+]
]
MachineName: <MachineName>
Method: RunJira_ProcessProject_SyncAgileCraftToJira
ProcessingType: Serial
Product: AgileCraft_Jira
ProgramId: 17
ServiceName: AgileCraft_Jira_<Customer>_1
ThreadId: 3
}
RenderedMessage: CreateFeatureInJira:Failed to create Jira issue for Feature
Timestamp: 2022-09-13T15:58:14.7525263+02:00
}
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- resolves
-
ALIGNSP-15911 Loading...