Scroll to top
en pl

Team communication – how to improve it with Jira


Ewa Jakubiec - 13 June 2019 - 0 comments

You’ve probably found yourself in a situation where during the review, it turned out that someone in your team didn’t see new information that was added during the sprint. We always wonder in such moments whether it’s the negligence of this person, a system error, or the employee had just too much work on their mind.

There are many possible explanations for a given situation, but the essence of it still remains the same: the message was not delivered to the recipient. Depending on the importance of this information, the consequences may vary. If the message was not so important, then most likely you will just execute it in the next sprint. In another situation, such an unread message may have a negative impact on the work.

Email notifications

How to avoid such situations? There are several solutions. The notification of changes arriving in the email inbox is definitely basic. However, not all employees may be used to checking their mailbox. They may not need it in their daily work, so they only use it several times a day.

Useful Jira Dashboard

If we know our team well and we know that in everyday life team members don’t use email that often, we need to think about a different solution. An example of that can be gadgets added to the Dashboard which display the latest application updates. When you enter Jira, you instantly see what has changed on a given day. That makes it very easy to work as it’s hard to miss new information.

Slack’s integration with Atlassian tools

The complementary solution to the two outlined above Slack which can also notify us about changes. If we properly configure the connection between our messaging app and Jira, our team will receive such notifications instantly.

External team communication with Jira

Unfortunately, a seemingly easy situation can turn into a more complicated one. The above solutions will always work, but in some cooperation models we have to apply additional mechanisms.

Sometimes, our project needs support from people from another team, for example, the system administrators. In such situations, communication may be difficult because both teams must manually create new entries to communicate.

Another circumstance is cooperation with a team which is external to our Jira installation. In such a situation, the Project Manager becomes the connector responsible for transferring the findings and changes from one application to the other – and remembering to give updated information to the teams.

The solution to this situation is the implementation of IssueSYNC, thanks to which applications, problems, and comments can be synchronized on a regular basis. The app will work both when we want to combine issues within one Jira instance and when two separate applications are combined.

Using the above solutions, your team can avoid many unpleasant situations. However, apart from these methods, it’s also worth using these four teamwork rules that will improve cooperation using Jira.

Related posts