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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How to have more visibility on technical customers about work

I just started with Jira, I see in the task little interaction that only shows the task to complete, and a comment saying done. What best practices are recommended to show the customer that engineers are progressing, and have some sort of proof  of work in the task itself.

usually related to confection of technical documents (i would like to know the source of information), bugs and code adaptations, and APIs.

1 answer

0 votes
Jack Brickey Community Leader Nov 29, 2022

Hi @Diego Galan ,

welcome to the community. Ultimately the right answer here is what works for you and your team. Particularly what do your "customers" require? Answering this will help you configure your projects and your processes to meet those needs. Now with that said, here are some initial thoughts.

  • ensure that your workflow indicates progress is being made. For example, include an In progress status and if appropriate Testing.
  • include regular progress comments that the customer/reporter will see
  • Be sure that the team process includes a final comment on how the issue was resolved, e.g. developed new feature, root cause of the bug was xxx and I did yyy to address.

Suggest an answer

Log in or Sign up to answer