You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep going to resume Roadmap. But what we will do with Projects then? Remove?
Smoothly end checkboxes in Roadmap, close it and new Issues tagged under Projects.
Why we need to have both Roadmap and Projects cards? It makes no sense and this bring more work.
Ok, let's think about it from point of view practicality:
Roadmap in one place, and this is good.
But Cards will be in one place too after setting Project on issue. [draw]
When adding in Roadmap we need to set «Roadmap» label on issue, open Roadmap Issue, find where we can checkbox and how he will called, and, paste link to issue near that checkbox.
And when we add to card, we will define Project on issue faster and then just define to that issue priority in Projects tabs (if needed). [W2]
Every time Roadmap issue growing more and more. More checkboxes, more comments. Revisions are hard for viewing and impossible to editing (only delete is possible). BTW, when I edit Roadmap issue I always use browser search by issue number to find what I need...
Cards editing more simply. They can be archived or deleted. They easier for visual perception, they colorized and we see all tags on all issues directly from Cards. And we can open issues directly inside Projects tab by clicking on any Card. [W2]
And finally, when we close issue with Feature Request or Bug Fix, we need to go in Roadmap, find that issue for editing it again, checking box for this issue and adding corresponding Pull in which this issue was Solved.
Cards will closed automatically. If issue was closed (auto-closing by Pull), card will auto-obtain Solved status too. [W2]
So, dudes, need to think about it and vote for better variant. With smooth closing of Roadmap issue. They don't was automatically several years ago, that's why I was create Roadmap. But for now we have another situation and can save our time easily.
I was see some disputes about Roadmap.
So, we need to decide what we will use.
Why we need to have both Roadmap and Projects cards? It makes no sense and this bring more work.
Ok, let's think about it from point of view practicality:
But Cards will be in one place too after setting Project on issue. [draw]
And when we add to card, we will define Project on issue faster and then just define to that issue priority in Projects tabs (if needed). [W2]
Cards editing more simply. They can be archived or deleted. They easier for visual perception, they colorized and we see all tags on all issues directly from Cards. And we can open issues directly inside Projects tab by clicking on any Card. [W2]
Cards will closed automatically. If issue was closed (auto-closing by Pull), card will auto-obtain Solved status too. [W2]
So, dudes, need to think about it and vote for better variant. With smooth closing of Roadmap issue. They don't was automatically several years ago, that's why I was create Roadmap. But for now we have another situation and can save our time easily.
Voting
http://www.easypolls.net/poll.html?p=5c8ce46be4b070a0255c16f5
The text was updated successfully, but these errors were encountered: