Each team has its own unique workflow. Why shouldn't notifications be unique as well? A timely reminder for one team may be something that arrives a day late for another. Our new update lets you adjust your notification schedule as you see fit. So if you want to notify about vacations one week in advance, and remind developers about issues that haven't been updated in the last two days, now you can do just that. Any combination is possible. A reminder should come at the right time. Now you can select the combination that will be perfect for your team.
Sometimes, developers become stuck. It happens to all of us, even the best and brightest. Maybe the requirements are not clear enough, or maybe there's a tough technical problem. In these situations we may need the help from others. New notification type "No recent commits" helps identify such situations and make it easier for the team to make progress.
We've added basic support for issue tracking for Github and Gitlab. If
you're using one of these platforms, Teamplify will automatically index
both open and closed issues in all of your repositories and show them on
the Team Activity page, with no user action required. You can also use
Due Dates or Pending Questions notifications for Github or Gitlab
issues, or track issue mentions in Slack (use
format to refer to an issue in Slack).
Please note that, while we can index open and closed issues, we don't currently analyze information about issue assignments. So, notifications for Issue Updates or Issues in Progress are not functional for Github/Gitlab issues yet. Stay tuned for updates!
Introducing a new notification type - Pending Questions. It notifies about questions in the issue comments that have remained unanswered for longer than one day. This will be helpful for discovering issues that are stuck in discussion and pushing them forward. Try it out for your team today!
Our most requested feature is here! Teamplify's happy to announce that we are now offering an on-premise installation of Teamplify.
Cloud installations make perfect sense for many teams. They’re secure, easy to set-up, and don’t require any work for maintenance or upgrades. But even in our SaaS era, cloud deployment is still an absolute no-go for some teams.Maybe you work in an industry with tight regulations or advanced security requirements. Or perhaps you need be able to see exactly where your data is kept. There are plenty of good reasons why a team may need to keep things on-premise. We here at Teamplify are excited to know that we now have a installation for server instances.
Under the hood, both installations work exactly the same. Teamplify on-premise simply allows you to run Teamplify behind your own firewall and with your data kept completely in-house. You'll still be be able to organize your work and reports exactly as cloud-based teams have already been doing.
On December 19th, 2018, Teamplify will upgrade its database to Amazon Aurora. As a result of this planned migration, our services are going to be unavailable for a short period of time. We expect users to be affected for about ten minutes between the hours of 0300 and 0400 UTC.
The outage will be necessary as we move our database to Amazon Aurora. We’ll be taking advantage of the downtime to improve user security with DB storage encryption as well.
As Teamplify grows with your business, we want to make sure that we have a database that will scale to an ever-increasing amount of work performed. Our move to Amazon Aurora allows us to meet this need, no matter the size of the team or the nature of its demands. Furthermore, Amazon Aurora is simply faster. Considering all the benefits for us and our customers, the decision to equip Teamplify with a database that’s fast, scalable, and ready for any occasion is an easy one to make.
However, we’re not just going to be upgrading our database’s horsepower— we’re also improving its security. The new database encryption will ensure that all the data in the main DB storage, logs, and backups stays encrypted.
For teams that want to stay light, Jira's Cloud service is a great option. But some teams need to be able to manage all the details of their project. We understand that, and it's why we’ve upgraded Teamplify to support teams on both Jira Cloud and Jira Server.
Just because your team prefers to use Jira Server doesn’t mean it can’t have its own trusty personal assistant. Teamplify already has been helping Jira Cloud users organize teams of all sizes. Now on-premise Jira teams can also analyze work progress, aggregate data from Jira into automated progress reports, and receive reminders about issues that may need some attention, like overdue tasks or projects that haven't been updated in a while.
There are many good reasons for a team to take on the extra complexity of hosting Jira itself. Coordinating that team, however, doesn’t need to be complicated. Let Teamplify make it easy for you. Besides the integration procedure, Teamplify works exactly the same on both versions of Jira. Why not try Teamplify with your Jira Server today?