You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Starting with Profields 6.5 for Jira Server and Data Center, users who watch a project will receive an e-mail highlighting the project custom field that has changed, the old value and the current value. Here’s how it looks:
Of course, many users can be interested in following multiple projects, but don't need to track every change as it happens. For them, the best option is to create a subscription to a query in the Project Navigator (available since Profields 6.6.0 in Server & Data Center).
The result is an email with a comprehensive summary table, like this one:
With many concurrent users come frequent changes in the Profields database, often affecting strategic projects and projects with numerous stakeholders. But until now there was no form of automating the communication of project changes: if the end date of a project was postponed, whoever made the change had to write an email to all stakeholders or rely on confluence macros –hoping that those interested would take the time to look at them and identify what had changed.
That’s why having the ability to watch projects is a very big leap forward for complex, project-intensive organizations.
Project fields are not likely to change as often as issue fields, but if you start watching many projects, emails can pile up rather quickly until you stop caring.
Here are some basic recommendations to make you a vigilant and sustainable project stakeholder. In general, it's important to choose wisely when to watch and when to subscribe.
Typically, when a company implements Profields successfully it’s for a combination of at least four different factors: a clear use case, a precise field taxonomy, user onboarding, and use policies.
The specific responses to the four factors will define who uses Profields, how they use it and when they use it. The range is very broad, from administrators only (albeit enjoyed passively by the entire user base) to a much broader base of active users with permission to create and modify project data.
The latter is a common response in enterprise customers: in those environments, the ability to watch helps create a sense of awareness about the status of important projects in Jira, supports the enforcement of change management policies and offers process transparency.
At the same time, project subscriptions are a perfect way to enforce automated project communication. Provided that you implement metrics and KPIs in your projects, it's easy to use subscriptions as your weekly project report.
In the near future, our team will implement important improvements:
Watch this article for updates!