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
Dear Atlassian Community!
We have purchased JIRA and Confluence Atlassian product enterprise licenses for quite some time.
Our ongoing iOS application project is also supported by these Atlassian products. At the moment we are past publication to Appstore.
The design and development product phases went quite well with the help of Atlassian products (JIRA, Confluence).
Now, after publication we are transitioning from design & development to Maintenance & Support product phase, in which maintenance activities are expected paralell to new feature development and bug fixes and technology (iOS or swift) upgrades and changes.
Please advise on tools, techniques, best practices on how to professionally handle the “maintenance & Support” phase with the help of Atlassian tools, products.
We are kindly asking, beside the above mentioned general question answers for the following specific dilemmas and questions:
- how to professionally handle periodically repeating activities (maintenance, marketing etc.) or
- are there best practices to handle maintenance type of activities (for example maintenance type sprints)
- how to handle paralell the new feature development type sprints and maintenance type sprints.
- are there any best practice issue types, workflows, confluence templates that support professional support & maintenance product phase handling.
Thanks for your thoughts and replies in advance.