• 7
    • 9
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Similar to POST functions that are set AFTER a transition is executed (after pressing e.g. the 'Resolve issue' BUTTON), it would be very useful to also be able to set PRE functions (values set in the transition view after the Available Workflow Action LINK is pressed = BEFORE the button is pressed).
      Thus, it is possible to set default values in the transition screen, but the user can still change it.

      E.g.:

      • press Available Workflow Action link 'Resolve issue'
        (invisibly, the assignee is set to the Reporter by the PRE function)
      • enter the screen which is set in the Transition View of the 'Resolve issue' transaction
      • here, the assignee is set to the default value Reporter; but the user can still change it
      • press the Resolve issue button to confirm

          Form Name

            [JRACLOUD-13604] Ability to initialise field values for a transition screen

            IT's important to have this feature, it's so demanded in our daily administration.

             

            FTITI Walid added a comment - IT's important to have this feature, it's so demanded in our daily administration.  

            Yes please, this would be a great feature as we need to populate a field during a transition not after the transition has been completed.  

            Janusnet Web Admin added a comment - Yes please, this would be a great feature as we need to populate a field during a transition not after the transition has been completed.  

            This would make my life so much easier as it would keep me from having to create all of these workarounds in workflows/transitions/automations.

            Andrea_Lawrence added a comment - This would make my life so much easier as it would keep me from having to create all of these workarounds in workflows/transitions/automations.

            I need this.  Please do it.  Thanks.

            Phil Bustin added a comment - I need this.  Please do it.  Thanks.

            This features should increase the usability of Jira cloud.

            It is actually not acceptable that users have to use expensive third party apps for such minor features

            Erik Mathijs added a comment - This features should increase the usability of Jira cloud. It is actually not acceptable that users have to use expensive third party apps for such minor features

            My use case is the creation of fields for standardization of collecting details from the emails so that a BOT can gather the data. This is resulting in more clicks for the user that could be reduced by adding a default for the "most common" answer in the fields.

             

            Cheryl Anderson added a comment - My use case is the creation of fields for standardization of collecting details from the emails so that a BOT can gather the data. This is resulting in more clicks for the user that could be reduced by adding a default for the "most common" answer in the fields.  

            jcron added a comment -

            To simplify UX (user experience) during workflow configuration, a new kind of post-function (called "display the transition screen") could be add to the post-function list instead of having the specific property to define transition screen

            Thus we can set a value (and do other stuff) before displaying transition screen ...
            It only depends on the position of this new kind of step ("display the transition screen") among others in the list of "post-functions"

            What do you think about this idea?

            jcron added a comment - To simplify UX (user experience) during workflow configuration, a new kind of post-function (called "display the transition screen") could be add to the post-function list instead of having the specific property to define transition screen Thus we can set a value (and do other stuff) before displaying transition screen ... It only depends on the position of this new kind of step ("display the transition screen") among others in the list of "post-functions" What do you think about this idea?

            My use case example would be that we want a "reviewing" step in our workflow which is not equated with "resolved". This is achieved by having resolution set only on "close" - but we'd like it to default to the value set on a custom "Resolution (Pre-review)" field set by the person sending the issue for review (i.e. set in the transition from In Progress to Reviewing). This can't be achieved with a post-condition, because the person "Closing" the issue might decide a different resolution is appropriate and a post condition would overwrite that.

            In this case, if the transition is cancelled the pre-initalisation should be ignored.

            Bob Campbell added a comment - My use case example would be that we want a "reviewing" step in our workflow which is not equated with "resolved". This is achieved by having resolution set only on "close" - but we'd like it to default to the value set on a custom "Resolution (Pre-review)" field set by the person sending the issue for review (i.e. set in the transition from In Progress to Reviewing). This can't be achieved with a post-condition, because the person "Closing" the issue might decide a different resolution is appropriate and a post condition would overwrite that. In this case, if the transition is cancelled the pre-initalisation should be ignored.

            My Kro added a comment -

            I am evaluating JIRA for use in my organisation and found the lack of this feature curious. My use case is that I have an explicit transition and screen for "Resolve unchanged" as opposed to "Resolve". In that transition I want the Resolution to default to "Won't Fix", but to still support the selection of other resolutions.

            My Kro added a comment - I am evaluating JIRA for use in my organisation and found the lack of this feature curious. My use case is that I have an explicit transition and screen for "Resolve unchanged" as opposed to "Resolve". In that transition I want the Resolution to default to "Won't Fix", but to still support the selection of other resolutions.

            I also support this request, it would be nice to initialize some values of visible on invisible fields before showing the transition screen in a "pre-function" but also would like to:

            • have the possibility to add these "pre-functions" on a transition, the same way one can add post-functions
            • if the transition is cancelled, some of the values set should be ignored (e.g. duration until the issue is being processed) and some not (example a counter of clicks). Since I hardly can/cannot have both I would prefer to have the initialized values ignored

            Florin Haszler (Alten Kepler) added a comment - I also support this request, it would be nice to initialize some values of visible on invisible fields before showing the transition screen in a "pre-function" but also would like to: have the possibility to add these "pre-functions" on a transition, the same way one can add post-functions if the transition is cancelled, some of the values set should be ignored (e.g. duration until the issue is being processed) and some not (example a counter of clicks). Since I hardly can/cannot have both I would prefer to have the initialized values ignored

              Unassigned Unassigned
              2236ff10e5ed Sabine Van Regenmortel
              Votes:
              118 Vote for this issue
              Watchers:
              54 Start watching this issue

                Created:
                Updated: