Often we need to capture an idea, or a felt need, without yet knowing whether the idea will actually be worked on, or by whom. How do we capture and track those ideas, yet keep them separate from tasks that are approved to be worked on? E.g.
This is something I've wondered about for years, as I've used JIRA. I'm wondering both,
Two different scenarios that I have seen in my experience, both of which you have touched on but just adding my 2 cents.
Firstly, I believe Idea and Task should be easily distinguishable and hence be of different issue types.
Think about issue creation. It will be misleading to the user if they are just submitting an idea but they need to create a task. Depending on your org, you can handle this with training but user experience wise, it is much clearer for users submitting ideas to create an Idea issue type.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs