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
Does anybody find using the word ISSUE for Project Tasks misleading? In Project Management, Risks & Issues are distinct items and shouldn't be confused with tasks.
Unfortunately this is a fairly built-in term used by Jira, and probably quite cumbersome to change. It dates back to when Jira was essentially just a bug/issue tracking tool. Everything in Jira is referred to as an "issue", and yes it does cause confusion with new users. This is usually the first thing I explain to new users during training.
If you actually want to track Risks & Issues for your project, I would suggest creating a new issue type for "Risk" and maybe one called "Project Issue". We have a similar issue type called RAID, with a custom field to state which RAID Type it is.
Hope this helps.