• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 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.

      Requested by @littlefyr on Twitter, he'd like the ability to have prompts come up for parameters when a Custom Action is invoked, for cases where the parameters may vary per invocation.

      He suggested quite a complex format for this including types, option lists and ranges but I think that's a bit overkill, and a simpler name/value association would work fine. So something like "$prompt(<name>)" where the dialog includes '<name>' as the parameter label.

            [SRCTREE-942] Support parameter prompting in Custom Actions

            Arati Mohanty (Inactive) made changes -
            Assignee New: Arati Mohanty [ 2566180e0bc8 ]

            lasse added a comment -

            Custom actions are borderline useless without this. Please get it implemented.

            lasse added a comment - Custom actions are borderline useless without this. Please get it implemented.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3371461 ] New: JAC Suggestion Workflow 3 [ 3671672 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: SourceTree Bug Workflow [ 376130 ] New: JAC Suggestion Workflow [ 3371461 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Monique Khairuliana (Inactive) made changes -
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]

            This has been an outstanding issue for 6 years, can we please get this implemented?

            Michael Zipp added a comment - This has been an outstanding issue for 6 years, can we please get this implemented?

            Ziv Wities added a comment -

            I'd really like to see this one implemented. It would be a major asset in bridging between GUI and command-line – we'd be able to turn simple command-line actions into established GUI actions, so when my team needs some slightly-different action available in their everyday workflow, they can have it available (without needing to switch over to the command line).

            Ziv Wities added a comment - I'd really like to see this one implemented. It would be a major asset in bridging between GUI and command-line – we'd be able to turn simple command-line actions into established GUI actions, so when my team needs some slightly-different action available in their everyday workflow, they can have it available (without needing to switch over to the command line).

            I need this to create a custom action that does e.g.

            git checkout -b [USERINPUT] branch-to-start-at
            

            Henning Klokkeråsen added a comment - I need this to create a custom action that does e.g. git checkout -b [USERINPUT] branch-to-start-at
            Brian Ganninger (Inactive) made changes -
            Symptom Severity New: Minor [ 14432 ]
            Assignee Original: Steve Streeting [ sstreeting ]

            I also would need to set a name for a branch (to start a bugfix branch, since it isn't included in the git-flow actions)

            Daniel Kloeck added a comment - I also would need to set a name for a branch (to start a bugfix branch, since it isn't included in the git-flow actions)

              2566180e0bc8 Arati Mohanty (Inactive)
              sstreeting Steve Streeting (Inactive)
              Votes:
              40 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: