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.
Thank you, this is helpful. If you have an "Ideation" status, don't you think it would be redundant to have an "Idea" issue type, since you could easily distinguish ideas from tasks by their status?
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.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events