Jesse
My feedback
39 results found
-
1 voteJesse
shared this idea
·
-
2 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment Jesse
supported this idea
·
-
1 voteJesse
shared this idea
·
-
6 votesJesse
supported this idea
·
-
7 votesJesse
supported this idea
·
-
1 voteJesse
shared this idea
·
-
1 voteJesse
shared this idea
·
-
1 voteJesse
shared this idea
·
-
3 votesJesse
supported this idea
·
-
9 votesJesse
supported this idea
·
-
38 votes
We're currently reviewing how we can facilitate deployments to multiple Salesforce instances simultaneously. Please let us know how you manage this currently, or how you would like to manage it - thanks!
Jesse
supported this idea
·
-
12 votesJesse
supported this idea
·
-
2 votesJesse
supported this idea
·
-
20 votesJesse
supported this idea
·
-
4 votesJesse
supported this idea
·
-
7 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Jesse
supported this idea
·
-
3 votesJesse
supported this idea
·
-
2 votesJesse
supported this idea
·
-
3 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Jesse
supported this idea
·
-
10 votesJesse
supported this idea
·
We also face the same issue. We want to require Jira tickets for deployments to a specific set of deployment targets, whether they come from a pipeline PR or an ad-hoc Compare and Deploy. We don't see a need to require Jira tickets when the target of a deployment is a less important org like a random developer sandbox. This type of flexibility would also solve more use cases like if a team wanted to specifically enforce Jira tickets while deploying to a specific source control branch but not another one.