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

Move an issue or create a new one for new fiscal year?

Hello Jira community!

We use Jira Server to manage technology implementation projects and support for our customers.

What is the best practice for tracking billable time on an existing issue that will now be worked on in the new contract year while providing continuity to our team providing support on that issue?

When we offer support, most times the customer, more often than not, customer renews the contract to the next year. We track the total hours allowed on the contract on an Epic called Support, and create issues for specific requests and track our billable time on those in Tempo.

When we get a contract extension or a new contract with the same customer, should we - 

 - move the existing issue that was worked on to a new project (say support 2024), and tie it to a new Epic (2024 support) so the team can see what has been done on the issue until now, then track time on this existing issue?


- create a new issue under a new project and tie it to a new epic, and track time on the new issue, which means they will need to be flipping back to the old project to see what was done.

Thank you for your help!

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events