Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,658
Community Members
 
Community Events
176
Community Groups

How to leverage JIRA to track human work outside of the activity log - Slack

Hey folks,

I have been wondering about how to leverage JIRA to manage all the human work for issues and bugs that goes on outside of the JIRA Activity log.  For example when dev team are all in on Slack usage, lots of the key information is located in Slack in the back and forth dialog.  There may times where we want to add a comment to the JIRA bug or issue, which we do from Slack with a Slack App, but I am wondering about how everyone handles the rest of the useful information that resides in Slack?

1 comment

Yes we use that, but my question was more about what about all the dialog that occurs in the slack channel,   lots of information is lost there, unless every Slack message is done as a comment....   2020-03-25 09_57_21-Slack _ Jira Cloud _ RigD.png

Comment

Log in or Sign up to comment