Move Work Forward helps professionals, teams and organizations to increase productivity, team transparency and connect tools together.
We remote-only bunch of folks who build and run apps for Atlassian Jira, Confluence, Bitbucket, Bamboo and Microsoft Teams, GitHub, Azure DevOps, GitLab, Gerrit and Slack.
Our apps are used by thousands of organizations all over the globe. We are trusted by companies like Apple, Microsoft, Amazon, Tesla, SpaceX, NASA, Sony, Samsung, Dell, etc.
if i trigger pipeline in repository,the build status is replicating all the tickets. anything is there to avoid replicating build status to multiple issues
Hi Budd, I'm planning to ask for this tool at my current job since we can't get rid of the Errors log when some build fails for some reason. This is common since I'm a tester so I'm used to have like 7 of 30 test cases failing. I saw in other of your videos that it is possible with your connector (because your notification channel had errors with no logs). However, I want to be sure that your tool in it's current state matches my needs, can we customize easily the message that bamboo sends to ms teams? also, is it possible to achieve what I want without using any external tool or plugin? If so, do you offer helping/training sessions? best regards
Hi and thanks for writing. I suggest you reach out to our support and we jump on a call and review your setup and issues. You can do it here - moveworkforward.atlassian.net/servicedesk/customer/portal/1
I agree this product has been rushed to general beta before it is ready in order to add a feature that Notion has. Whiteboards was done well. But Atlassian needs more time to make Confluence Databases (why is it not called tables?) good.
Check out GitHub, GitLab, Gerrit integration with Jira Data Center from Move Work Forward - marketplace.atlassian.com/apps/1217129/jigit-jira-github-gitlab-integration?hosting=datacenter&tab=overview
As far as I can see there is absolutely no support for multiple tables that are semantically related. That is, you cannot have multiple primary keys, foreign keys nor enforcement of referential integrity or indeed uniqueness. If I am wrong, I'd love to know cos that would make these "databases" infinitely more useful.
Hello Move work forward channel admin. I visited your channel and your video is very nice but your video has no views and no subscribers. The only reason your videos aren't going viral is because your videos aren't seoed Your video must be SEO friendly How can I contact you?
Hello Move work channel admin. I visited your channel and your video is very nice but your video has no views and no subscribers. The only reason your videos aren't going viral is because your videos aren't seoed Your video must be SEO friendly How can I contact you?
Hey Leo! Thank you for reviewing Excel-like Tables for Confluence! I completely agree with you that currently, it works as an embedded Excel in Confluence, but it's not integrated with Confluence. We do have it in our backlog to tag/mention Confluence users on the table, and we'll reassess whether to prioritize this feature. We'll definitely showcase a better version to you during Team '24 in Vegas this year! 😄 Cheers, Razi
The detailed Atlassian Community post - community.atlassian.com/t5/Jira-Software-articles/How-to-Use-Jira-Automation-with-Azure-DevOps/ba-p/2579496#M12228 Azure DevOps for Jira - marketplace.atlassian.com/apps/1231122/azure-devops-for-jira?hosting=cloud&tab=overview
Hi, great app. Working fine except one thing, that's why I have a question. It's regarding Deployments section in Jira. How the Azure CI/CD Pipelines Environment is mapped to Jira Deployment Environment? For me, it always shows Staging in Jira, even if it was Production env pipeline deploy on DevOps. Is it linked by branch name, pipeline stage name, or any other DevOps key?
Hi, There is a stage parameter in the pipeline and we process it. If possible please contact our support and share where you define your stages. moveworkforward.atlassian.net/servicedesk/customer/portal/1
I got a trial for jira-azuredevops integration. However, when I select create branch in my tasks, it does not direct me to the azure devops screen. It just gives me the text from which I can create a branch for Git. Does this plugin not help me create a branch directly via Jira? Please support me? Cannot create branch jira via azure devops
Thank you for your comment. Please create the support request to track your feature request moveworkforward.atlassian.net/servicedesk/customer/portal/1
Hello @moveworkforward, I managed to make your plugin work but release info seems to be stuck in "In progress" status forever. Do you have any idea what could be thé problem here? Thanks for the info.
Bitbucket Slack integration application for notifications is here - marketplace.atlassian.com/apps/1213042/slack-notifications-for-bitbucket?hosting=datacenter&tab=overview
Hi there @moveworkforward, can you confirm if branch naming allows for usual git flow names too? e.g. feature/DEV-4-sometask. Can you also confirm if there is any way to link a branch to multiple jira tickets, e.g. if a single branch fixes multiple bug tickets in jira
Hello @sarah, Thank you for asking. 1. The Git flow is supported. You can use Jira issue key inside your branch name. 2. You cannot use multiple issues inside a branch name. We can see if we can implement this. Could you please show a few examples of how do you use this. However, commits and pull requests support multiple issue keys inside the commit message or PR title. 3. Because of the 2nd you can see commits, PRs, builds from a feature branch against multiple Jira issues. Hope it helps. Thanks, Leo
