Implement support for issue transition screens
Description
Add functionality to support issue transition screens when transitioning statuses.
Allow the edition of issue fields during a status transition, removing the previous limitation where status changes were blocked when a transition screen was required.
Accepted criteria
Issue transition screens should be enabled during status changes.
Status change should no longer be blocked when transition screens are required.
Linked issues
relates to
ESFJ-877
Enable issue and custom field population in issue creation for external users
ESFJ-877
Enable issue and custom field population in issue creation for external users
Released
Activity
Show:
Details
Priority
MediumAssignee
Mykhailo Iereshchenko
Reporter
Parsa Shiva
Labels
feature_requestroadmap
Time tracking
4w 4d 7h 20m logged
Fix versions
Roadmap
Created
18 September 2024, 10:43
Updated
3 February 2025, 11:43
More fields
Created: 18 September 2024, 08:43
Updated:
3 February 2025, 10:43
also can’t figure out [CHART] Date of First Response gives me error in jira, because of that i can’t update this field in ES. It’s supposed to be for JSM projects.
maybe we can remove it for now?
unable to update ‘Environment’ field
unable to change status by adding an attachment to a description field or directly to ‘Attachment’
@Mykhailo Iereshchenko
custom field (ex. ‘labels’) values are not populated during status transition
https://esfj.app.qa1.pl/issue/b64c15aa-f6da-41e6-a472-ef36b7cca470
@Polina Naumenko It should work now
unable to change a status, checked multiple instances
@Mykhailo Iereshchenko
Hello @Mykhailo Iereshchenko,
Change was reviewed and approved.
Task is ready to be deployed to QA.
Once it is deployed to QA please move ticket to "To Test"
Thank you!
@Mykhailo Iereshchenko Ok
@Krzysztof Bogdan We need to decide what to do with sprints. If we want it to behave the same way as in Jira (typing and dynamically searching for the matches using greenhopper) I propose that we disable sprints in this task and create a new one to add appropriate input type and support it. Will this be ok?
@Mykhailo Iereshchenko What is status of this ticket?
before all the issues below - the main problem i can't change a status dues to an error “Unknown problem occurred. Transition has not been completed“
In jira, there are no issues with a transition
@Mykhailo Iereshchenko
dark mode is not supported
is field Responders, Goals, Log Work, Design, Checklist Completed, Organizations, Checklist Progress %, Sprint, Checklist Progress, Project overview status, Project overview key, Request Type, Affected services supported?
Date type of fields look ugly now, should be a calendar available
ex. Satisfaction date, Start date, Actual start, Actual end, Target start, Target end, [CHART] Date of First Response, Due date
existing description is taken in Jira, ES field is empty
Story point field consists of spin button (up and down arrows), Jira doesn’t
Change type, Change risk, Change reason, Impact, Pending reason, Severity, Urgency to be displayed “None” by default
Service management project - selected fields are not displayed (Pending reason)
for testing:
Add transitions
Configure screen with selected fields
Add Validators (mandatory fields)
Hello @Mykhailo Iereshchenko
This is the best moment to add more information that can be helpful for tester.
What areas are affected?
What are potential edge cases?
Was it checked for XSS problems?
Does change affect security, is new data exposed?
Please attach - Before / After screenshot if possible.
Hello [~accountid:],
Task is ready for review.
@Mykhailo Iereshchenko please make sure reviewer
have easy access to contend to be reviewed.
If this is code change. Please make sure PR is created.
If this is new documentation, blogpost, etc. Please provide link to page.