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

      Problem Definition

      We released new set of trigger called DevOps New automation triggers across Jira, Bitbucket and Github!. But this is now only available in Cloud instance.

      At the moment, the DevOps category is available, but no triggers under this option yet.

      Suggested Solution

      It would be great to have this available for Server and Data Center too.

            [JIRAAUTOSERVER-20] Having DevOps trigger in Server/Data Center

            yehsuf added a comment -

            Hi,

            Three years ago you already wrote in a community post

             It is not available natively in Jira Server / Data Centre but there is now an app in the marketplace from an Atlassian partner. 

            I think the time came that these capabilities that are provided by an external app should be available within the codebase.

            yehsuf added a comment - Hi, Three years ago you already wrote in a community post  It is not available natively in Jira Server / Data Centre but there is now an app in the marketplace  from an Atlassian partner.  I think the time came that these capabilities that are provided by an external app should be available within the codebase.

            Hi,
            we also need this functionality in Data Center. Please activate it, 

            thanks.

            BR
            Clemens Paul

            Clemens Paul added a comment - Hi, we also need this functionality in Data Center. Please activate it,  thanks. BR Clemens Paul

            Another example of total ignorance of customer requests. I also vote to have this implemented for Server/Data Center. Not that it matters...

            Honza Stekl added a comment - Another example of total ignorance of customer requests. I also vote to have this implemented for Server/Data Center. Not that it matters...

            the is very crucial for our instance, our customers depend on this to work

             

            Tiago Miguel Sousa Santos added a comment - the is very crucial for our instance, our customers depend on this to work  

            Joe Hewitt added a comment -

            It feels Data Center customers have been treated as second class citizens in the Atlassian ecosystem regardless of the fact that we are long time customers who have continued to invest in Atlassian for well over a decade. Our security and operational requirements prevents us from migrating our Data Center installations to the corresponding cloud offerings. 

            In this case, Atlassian owns the both sides of the integration, however they seem to choose to leave this capability out for Data Center customers as incentive to get customers on their Cloud platform. They have gone out of their way to support clients who have not invested in the full suite (Jira + Bitbucket Data Center) by adding support for Gitlab self-hosted and GitHub Enterprise, but intentionally neglect the product they have most control over. This can be perceived as we would be better off not using Bitbucket and migrating to Gitlab or GitHub instead. 

            I would love to see this perspective to be proven wrong. The fact that this story has been hanging around so long, I am not optimistic. I realize a comment on a story is not going to make a difference in the company's handling of existing customers with requirements to stay with Data Center edition. However, a few small wins like implementing this story can at least make the case that Atlassian is still considering the needs of organizations who are unable to move to the Cloud platform. 

            Thank you in advance for considering this feedback! 

            Joe Hewitt added a comment - It feels Data Center customers have been treated as second class citizens in the Atlassian ecosystem regardless of the fact that we are long time customers who have continued to invest in Atlassian for well over a decade. Our security and operational requirements prevents us from migrating our Data Center installations to the corresponding cloud offerings.  In this case, Atlassian owns the both sides of the integration, however they seem to choose to leave this capability out for Data Center customers as incentive to get customers on their Cloud platform. They have gone out of their way to support clients who have not invested in the full suite (Jira + Bitbucket Data Center) by adding support for Gitlab self-hosted and GitHub Enterprise, but intentionally neglect the product they have most control over. This can be perceived as we would be better off not using Bitbucket and migrating to Gitlab or GitHub instead.  I would love to see this perspective to be proven wrong. The fact that this story has been hanging around so long, I am not optimistic. I realize a comment on a story is not going to make a difference in the company's handling of existing customers with requirements to stay with Data Center edition. However, a few small wins like implementing this story can at least make the case that Atlassian is still considering the needs of organizations who are unable to move to the Cloud platform.  Thank you in advance for considering this feedback! 

            My interest in this capability is the same as those who have already posted a comment.  We are using Automation for Jira Rules extensively on our projects.  The additional features found in the Cloud version would be so very helpful.  

            jeff.l.taylor added a comment - My interest in this capability is the same as those who have already posted a comment.  We are using Automation for Jira Rules extensively on our projects.  The additional features found in the Cloud version would be so very helpful.  

            James added a comment -

            Yes please add this to DataCenter version. Need this so badly.

            James added a comment - Yes please add this to DataCenter version. Need this so badly.

            This would be immensely helpful for our teams.

            Natasha Veomett added a comment - This would be immensely helpful for our teams.

            Dave Liao added a comment -

            Would love to have these triggers in Jira Automation for Data Center - c'mon Atlassian, I'll buy you a few beers! 🍻

            Dave Liao added a comment - Would love to have these triggers in Jira Automation for Data Center - c'mon Atlassian, I'll buy you a few beers! 🍻

            Hi,

            We need it.

            Thank you,

            維珏(Vic) 許 added a comment - Hi, We need it. Thank you,

            Raju PSR added a comment -

            Hi,

            Please do implement this DevOps Trigger in Data Center too. As many users are using Jira Data center and these DevOps Functions are quite necessary.

             

            Thanks,

            Raju PSR added a comment - Hi, Please do implement this DevOps Trigger in Data Center too. As many users are using Jira Data center and these DevOps Functions are quite necessary.   Thanks,

            Hi,
            please implement these Devops triggers on Server as well. It would greatly benefit our team's workflow!

            Robin van der Stelt added a comment - Hi, please implement these Devops triggers on Server as well. It would greatly benefit our team's workflow!

            So why has this implementation not arrived at Jira DataCenter yet ? (almost 2 years on this ticket)

            (Not every company is happy with giving away it's data to cloud services...)

            Martin Papproth added a comment - So why has this implementation not arrived at Jira DataCenter yet ? (almost 2 years on this ticket) (Not every company is happy with giving away it's data to cloud services...)

            Would really love to have this. I have a client who is using on-prem Jira and as a company decision, they will not be using Jira cloud for a number of reasons. The Devops automation would immensely solve a number of workflow issues they have that the data-center version of the plugin does not have

            Matthew Bailey added a comment - Would really love to have this. I have a client who is using on-prem Jira and as a company decision, they will not be using Jira cloud for a number of reasons. The Devops automation would immensely solve a number of workflow issues they have that the data-center version of the plugin does not have

            John Price added a comment -

            We would really like these for Data Center.  We know that Cloud is the future, but it's 2-3 years away at least for our large organization.  We just purchased Automation for Jira Data Center and DevOps rules would be a huge hit with teams using GitLab and other tools.  

            See also https://community.atlassian.com/t5/Automation-articles/New-Build-and-Deploy-triggers-for-Jira-automation/ba-p/1442789#U1732722.

            I realize the code bases for the two versions of Automation are probably quite diverged, but we don't want to feel like our recent investment in the Data Center version was a mistake.  Please add this!

            John Price added a comment - We would really like these for Data Center.  We know that Cloud is the future, but it's 2-3 years away at least for our large organization.  We just purchased Automation for Jira Data Center and DevOps rules would be a huge hit with teams using GitLab and other tools.   See also https://community.atlassian.com/t5/Automation-articles/New-Build-and-Deploy-triggers-for-Jira-automation/ba-p/1442789#U1732722. I realize the code bases for the two versions of Automation are probably quite diverged, but we don't want to feel like our recent investment in the Data Center version was a mistake.  Please add this!

            We have released the Better DevOps Automation app just recently.
            It provides the following DevOps triggers for Jira Data Center and Jira Server:

            • Changeset Accepted trigger
            • Changeset Rejected trigger
            • Branch Created trigger
            • Tag Created trigger
            • Commit Created trigger
            • Genius Commit Created trigger

            See the trigger details.

            Aron Gombas [Midori] added a comment - We have released the Better DevOps Automation app just recently. It provides the following DevOps triggers for Jira Data Center and Jira Server: Changeset Accepted trigger Changeset Rejected trigger Branch Created trigger Tag Created trigger Commit Created trigger Genius Commit Created trigger See the trigger details .

              Unassigned Unassigned
              azuhra Aqqiela
              Votes:
              126 Vote for this issue
              Watchers:
              85 Start watching this issue

                Created:
                Updated: