This is only a minor issue but just want to see what ye think.
We have an issue with how Octopus names a newly added step, from a custom step template.
For example, a custom step template we created “GiveFullControlToFolder”, that we use in many of our projects.
On a project, if I add a new step, and select “GiveFullControlToFolder”, the new step on my project will have the name: “Run a script”.
The custom step contains a powershell script so maybe that is why it names the step “Run a script”.
It is not a big deal we just have to rename the step manually.
Thanks for reaching out.
I do believe this is intended behavior, but now that you bring it up I do see the value in having a configurable name for a step template when added to a process or have it use the step template name itself. I’m going to pass this along to our feature team for consideration in the future.
Please let me know if you have any other questions or concerns.
Thats great, Thanks a lot for your response.
Sorry for the misinformation, apparently this IS a bug.
Please follow the issue for updates going forward.
Please let me know if you have any other questions.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.