334 results found

1. Add Marketing Cloud as an option for Compares and Deployments

   Earlier this year there was a 'preview' option to allow for the Compare and Deploy features to interact with Salesforce Marketing Cloud orgs and business units. That option has gone away and I would love to have it back. As we support both CRM and Marketing Cloud it would be a great option to fold our Marketing Cloud configuration into our overall DevOps, especially around sending MC configuration and metadata to Github and different branches of a repository. In addition, it was going to be very helpful for moving configuration and metadata between different Business Units within a MC org as well. So, I would like to request that Marketing Cloud come back as a source and destination option in metadata deployment options to better incorporate MC into Salesforce DevOps processes.

   Earlier this year there was a 'preview' option to allow for the Compare and Deploy features to interact with Salesforce Marketing Cloud orgs and business units. That option has gone away and I would love to have it back. As we support both CRM and Marketing Cloud it would be a great option to fold our Marketing Cloud configuration into our overall DevOps, especially around sending MC configuration and metadata to Github and different branches of a repository. In addition, it was going to be very helpful for moving configuration and metadata between different Business Units within a MC org… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. How to Maintain Your Property After Bee Removal

   After a professional bee removal, maintaining your property is key to preventing future infestations. First, inspect and seal entry points such as cracks, vents, and gaps in walls or roofs to keep bees and other pests out. Regularly clean the area where the hive was removed, removing leftover honey, wax, and debris, which can attract new colonies. Trim overgrown trees and shrubs near your home, as these can serve as nesting sites. Consider planting bee-resistant flowers if you want to reduce activity close to your property while still supporting pollinators elsewhere. Lastly, schedule routine inspections with trusted experts—choosing a reliable Bee Removal Service in Oceanside, CA can ensure your property stays safe, clean, and bee-free. Proactive care helps protect your home and peace of mind.

   After a professional bee removal, maintaining your property is key to preventing future infestations. First, inspect and seal entry points such as cracks, vents, and gaps in walls or roofs to keep bees and other pests out. Regularly clean the area where the hive was removed, removing leftover honey, wax, and debris, which can attract new colonies. Trim overgrown trees and shrubs near your home, as these can serve as nesting sites. Consider planting bee-resistant flowers if you want to reduce activity close to your property while still supporting pollinators elsewhere. Lastly, schedule routine inspections with trusted experts—choosing a reliable … more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Mistakes to Avoid When Selecting a Mobile App Development Company

   Choosing the right Best mobile app development company can make or break your project, yet many businesses overlook crucial factors. A common mistake is focusing solely on price—cheaper options often sacrifice quality, communication, and long-term reliability. Another issue is failing to review the company’s portfolio; past work reveals their design style, technical skills, and ability to handle complex features. Many clients also skip checking client reviews or testimonials, which can expose red flags early. Additionally, not discussing post-launch support can lead to unnecessary hassles later. Always prioritize transparency, clear timelines, and a team that understands your business goals to ensure a successful app development journey.

   Choosing the right Best mobile app development company can make or break your project, yet many businesses overlook crucial factors. A common mistake is focusing solely on price—cheaper options often sacrifice quality, communication, and long-term reliability. Another issue is failing to review the company’s portfolio; past work reveals their design style, technical skills, and ability to handle complex features. Many clients also skip checking client reviews or testimonials, which can expose red flags early. Additionally, not discussing post-launch support can lead to unnecessary hassles later. Always prioritize transparency, clear timelines, and a team that understands your business goals to ensure… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Org Intelligence help us build correctly from the start rather than analyse a deployment. It will be great if it can be analysed as well
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Pick up test classes to run from the apex class

   Add a variable in apex classes where we can specify which test classes to run.

   Recently you added the ability to specify the test classes to run on a pull request, which is great!

   I know <ApexClassName>Test are automatically picked up by GS, but would be great if we could specify with
   @TestClasses('CaseTestSuite,LeadTestSuite') or similar in the actual Apex Class and Gearset would automatically pick it up and add those test classes to the pull requests .

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. AI-generated PR descriptions are availble only while creating PR and these descriptions are not currently present in the Pipeline UI , Can

   AI-generated PR descriptions are availble only while creating PR and these descriptions are not currently present in the Pipeline UI , Can someone please look into this and it's good if we bring that changes as well to the UI.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Enable the ability to use Capturing Groups as part of the replacement in Environment Variables when using Regex

   Twice now we have run into issues with deployments that would be satisfied by having the ability to use the capturing groups of the Regex expression in the Environment Variable to populate parts of the replacement.

   A good example of this is usernames in Assignment Rules. Salesforce exports the assignment rule metadata from a developer sandbox without the sandbox name on the end. So, in the metadata file it has user@domain.com instead of user@domain.com.sbx.

   In criteria you can also be filtering on email addresses, so if you just look for @domain.com in the environment variable, it will also find email addresses in the criteria for the same domain. If this is the case, you can use a look-ahead format in the Regex to exclude those email addresses from the environment variable, but that means you have to match on the entire email address and not just the @domain.com part. Therefore, you need to include the full username in the replacement into the pipeline environments in order for them to be deployed successfully. If you capture that in a capturing group in the regex, you can simply use $1.sbx to change the user names to the sandbox relevant user names.

   This has come up in another use case as well, but it would just be useful to have as a tool in GS.

   Twice now we have run into issues with deployments that would be satisfied by having the ability to use the capturing groups of the Regex expression in the Environment Variable to populate parts of the replacement.

   A good example of this is usernames in Assignment Rules. Salesforce exports the assignment rule metadata from a developer sandbox without the sandbox name on the end. So, in the metadata file it has user@domain.com instead of user@domain.com.sbx.

   In criteria you can also be filtering on email addresses, so if you just look for @domain.com in the environment variable, it will also find… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Remove "No Difference" items when commenting on jira tickets

   when i connect a jira ticket to a commit, I like the way gearset posts a comment on the jira ticket listing the changed items. what I dont like is the long list of "no difference" items posted on the ticket. It makes the ticket comments super long and annoying to scroll through. can gearset update this to only post the difference metadatas, or at least give us the option to include or exclude

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Automate upstream branch syncing

   After merging/deploying to prod allow auto-creation of sync PR's to upstream branches/orgs (QA, UAT, Staging, etc...). If the sync PR's could be promoted automatically that would be amazing.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add Pipeline Functionality to Handle Environment Refreshes and Branch Realignment

    In many Salesforce development workflows, environments (especially static ones like UAT or SIT) are periodically refreshed from production. When this happens, the environment’s metadata and configuration can become out of sync with the branch linked in Gearset Pipelines.

    This especially occurs when:

    • Changes were made directly in production that didn’t flow through the pipeline, but now exist in the refreshed sandbox.
    • A deployment was started partway through the pipeline but never completed to production, leaving partial changes held on branches in the repo.

    Currently, the workaround is to manually run a comparison and commit the differences to realign the branch. However, doing this also triggers a CI job unnecessarily, adding extra time to the process. In these cases, no actual feature changes are being deployed the goal is simply to bring the repo branch back into alignment with the refreshed environment.

    Ideally, I would like a way for Gearset to re-sync the branch to match the main branch or the refreshed environment directly. While it’s possible to create a new branch to achieve this, that approach causes loss of history and requires additional setup effort.

    Proposed Enhancement:

    Introduce functionality within Gearset Pipelines to:

    • Automatically reset or re-sync the associated branch, API version, and metadata state to reflect what’s actually in the refreshed environment when a static environment is marked as refreshed.
    • Provide an option to perform this alignment without triggering CI or deployment actions.
    • Optionally trigger an automatic comparison or rebuild of the environment’s baseline for visibility.

    This enhancement would help maintain pipeline integrity after org refreshes, reduce manual work, and prevent unnecessary CI job runs when simply re-aligning environments and source control.

    In many Salesforce development workflows, environments (especially static ones like UAT or SIT) are periodically refreshed from production. When this happens, the environment’s metadata and configuration can become out of sync with the branch linked in Gearset Pipelines.

    This especially occurs when:

    • Changes were made directly in production that didn’t flow through the pipeline, but now exist in the refreshed sandbox.
    • A deployment was started partway through the pipeline but never completed to production, leaving partial changes held on branches in the repo.

    Currently, the workaround is to manually run a comparison and commit the differences to realign the branch.… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Delete Flow by Version Number

    It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:

    • You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.

    • You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the version(s) to remove.

    It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:

    • You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.

    • You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be benefic

    I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be beneficial to have the option to allow a user to commit changes to a branch but block their ability to create a pull request (PR). This would allow our team to review the commits before a PR is opened, providing a more effective way to manage and correct any potential issues before they impact the main repository. This is an improvement that would significantly streamline our workflow and reduce the risk of errors.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Restore feature branch when a mid-flight promotion branch is restored

    Have just experienced a scenario where closing a PR that is mid-flight in the pipeline caused the promotion branch and underlying feature branch to be deleted. So far, so good in terms of expected behaviour due to my pipeline settings. However, after restoring the promotion branch in order to reopen the PR and promote it in the pipeline, the next environment on the pipeline did not then show the change. This, I believe, was because restoring the promotion branch DID NOT restore the feature branch. Therefore there was no source to create a new promotion branch from in order to open a PR for the next environment. Feels like we are missing functionality whereby restoring a promotion branch should also restore the feature branch, especially if the restored promotion branch is mid-flight in the pipeline - which should be identifiable through naming convention of the restored promotion branch in relation to the pipeline.

    Have just experienced a scenario where closing a PR that is mid-flight in the pipeline caused the promotion branch and underlying feature branch to be deleted. So far, so good in terms of expected behaviour due to my pipeline settings. However, after restoring the promotion branch in order to reopen the PR and promote it in the pipeline, the next environment on the pipeline did not then show the change. This, I believe, was because restoring the promotion branch DID NOT restore the feature branch. Therefore there was no source to create a new promotion branch from in order to… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Create a mass back propagation button

    Its very time consuming to have to back propagate one by one to each org. Please create a mass back propagation button.

    Also when back propagating where more than one connection to an org exists for instance our techdebt org has several admin connections and I have to hit update on all of them. Make the back propagation smart enough to know that it only needs one update rather than on each connection to the same org

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Make pre/post deployment steps conditional on developer sandboxes.

    Pre/Post deployment notes can be set to pertains to various static environments but they always apply to sandboxes after a back deploy. This should be conditional-- most of the time I only set them applicable to prod and they aren't applicable to developer sandboxes.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Ability to "Hide" Sandbox Groups on Pipeline Page

    In the Pipelines page, it would be very helpful if we had the ability to "hide" entire sandbox groups from view. This would make it much easier to quickly find and focus on the environments that are relevant to the logged-in user.

    Ideally, this "hidden group" setting would persist across logins and page refreshes, similar to how the "collapse group" feature currently works.

    I'm sure an "unhide groups" feature will be needed with this as well, in case a previously hidden group becomes relevant again.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Preserve Precision Selections through Fetching the Latest

    You're precision selections feature is absolutely amazing! Every time I use your tool it just gets better and better and this feature has me hooked. It's been huge with lightning web pages which often have multiple changes in UAT and need to be separated for deployment.

    We prep deployments before sending to UAT. Occassionally, there has been a big delay since the package was originally validated. If I need to go back to the original draft deployment and refresh the selected items to ensure I'm not overwriting something else that went out, the precision selections are cleared.

    1. There is a message that the precision selection is cleared - Thank You! It's helpful to know that happened.
    2. Once they get cleared, it's hard to remember which components had precision selection
    3. Once they get cleared, it's hard to remember which precision selections we're in the prior comparison for each component

    In a perfect world gearset could do something like a git rebase and attempt to apply the same selections with the current comparison. And when that isn't possible (as git rebase often is) to provide some route to have the original selections available for reference so I can confidently choose the correction selections with the current comparison.

    As an example, I have a lightning web page where I added a button to the highlights section and removed a component from the sidebar. After the refresh it could just show a brief diff of what was previously in there, auto-select it if the system can reason what it is, and if not flag it with context (e.g. removed component x from sidebar, not automatically mergeable, reselect manually).

    And short term, just some way to keep the components that were selected visible easily with a message that they previously had precisions selections would be a huge help.

    Thanks for the great work. Keep it up!

    ps - The fetch the latest is also one of my favorites. It's gotten so much faster to iterate on preparing deployments now that I can really precisely refresh just the metadata I know was changed!

    You're precision selections feature is absolutely amazing! Every time I use your tool it just gets better and better and this feature has me hooked. It's been huge with lightning web pages which often have multiple changes in UAT and need to be separated for deployment.

    We prep deployments before sending to UAT. Occassionally, there has been a big delay since the package was originally validated. If I need to go back to the original draft deployment and refresh the selected items to ensure I'm not overwriting something else that went out, the precision selections are cleared.

    1. There is a… more
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Deployment Failures in Pipeline

    The flow of a pipeline promotion is as such:

    1. Validate deployment to org
    2. (on success) Merge PR into base branch AND move PR to "Recent Promotion History" tab
    3. Deploy to org

    IF the deployment fails at that point, or is partially successful it would be great to denote that somewhere within the CI job within the pipeline. This would give the devs.admins more visibility into the true state of their features. Maybe we don't even move to the next environment until after a successful deployment.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Automatically Backfill Dev Environments with Pull Request When Changes Are Promoted Downstream

    Description:
    Currently, Gearset’s pipeline tool does a great job of back-propagating changes between static environments when a change is made further down the pipeline. However, this behavior does not extend to developer environments, even if the change originated from a feature branch tied to that dev environment.

    Problem:
    If a developer starts work on a branch in their dev environment, and then that branch is promoted down the pipeline (e.g., through UAT, Staging, etc.), and changes are made to the branch further down (e.g., hotfixes, last-minute edits), those updates do not automatically get proposed back to the original dev environment.

    This leads to:
    - Dev environments drifting out of sync with the branch they were created from.
    - Increased manual effort to merge updates back into a dev environment.
    - A risk of bugs or inconsistencies when developers continue work unaware of downstream updates.

    Proposed Solution:
    When changes are made to a branch in a static environment further down the pipeline, and that branch originated from a dev environment, automatically create a pull request to update the dev environment’s branch with those changes.

    This would:
    - Keep the dev environment aligned with the true state of the branch.
    - Reduce manual syncing and the risk of drift.
    - Improve collaboration and awareness for developers working on long-lived branches.

    Description:
    Currently, Gearset’s pipeline tool does a great job of back-propagating changes between static environments when a change is made further down the pipeline. However, this behavior does not extend to developer environments, even if the change originated from a feature branch tied to that dev environment.

    Problem:
    If a developer starts work on a branch in their dev environment, and then that branch is promoted down the pipeline (e.g., through UAT, Staging, etc.), and changes are made to the branch further down (e.g., hotfixes, last-minute edits), those updates do not automatically get proposed back to the original dev environment.

    … more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add Monday.com as a source for User Stories

    Add Monday.com as a source for user story integration

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating