-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Currently, the Roadmap width is fixed. This makes it difficult to display when showing a short-term roadmap, or more than 4 Qs on a page. It would be great if this was manually adjustable like the rest of the roadmap bars are.
- is related to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
[CONFSERVER-35511] [Roadmap Plugin] Allow roadmap width to be adjustable
Ruben Fitzsimons
added a comment - Any Updates? 
Swetha Uppuluri
added a comment - Any updates on this ? 
Dror Atariah
added a comment - So how can one change the width of the whole gantt diagram? 
John Price
added a comment - See link to CONF-36013. I still have the same problem originally mentioned in both issues. Adding Weeks doesn't solve it. I want to be able to have the macro occupy the full screen width (not 1/2 of it like you currently get with a 4 month roadmap).
John Price
added a comment - See link to CONF-36013 . I still have the same problem originally mentioned in both issues. Adding Weeks doesn't solve it. I want to be able to have the macro occupy the full screen width (not 1/2 of it like you currently get with a 4 month roadmap). 
Derek Sheeman
added a comment - Setting to weeks in inadequate, try working up a 4 month roadmap.
Month- the columns are far too narrow to be useful and the roadmap won't stretch out to fill even a tiny laptop screen.
Week - too many columns, can't visualize the roadmap on one screen.
Being able to have the columns manually or automatically widen to the width of the section the macro is sitting in would be ideal, as it is my team refuses to use the macro (not useful to them) and is just pasting power point pages into the confluence pages.
Also ... totally not resolved by adding a weeks feature as it does not address the Suggestion at all.
Derek Sheeman
added a comment - Setting to weeks in inadequate, try working up a 4 month roadmap.
Month- the columns are far too narrow to be useful and the roadmap won't stretch out to fill even a tiny laptop screen.
Week - too many columns, can't visualize the roadmap on one screen.
Being able to have the columns manually or automatically widen to the width of the section the macro is sitting in would be ideal, as it is my team refuses to use the macro (not useful to them) and is just pasting power point pages into the confluence pages.
Also ... totally not resolved by adding a weeks feature as it does not address the Suggestion at all. Hello guys,
We have recently implemented Roadmap planner timeline for both months and weeks.
You can view my initial comments over at: https://jira.atlassian.com/browse/CONF-36095?focusedCommentId=733802&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-733802
Nicolas Lance
added a comment - Agreed. I thought I could finally represent time in my project wiki pages but as I have 2 to 3 month projects this macro is unusable... 
Nicolas Lance
added a comment - Agreed. I thought I could finally represent time in my project wiki pages but as I have 2 to 3 month projects this macro is unusable... 
barbarat
added a comment - Agreed, please allow the width change of the columns. If I have a bar name that is too long (also can't adjust font size) then the bar name gets cut off.
barbarat
added a comment - Agreed, please allow the width change of the columns. If I have a bar name that is too long (also can't adjust font size) then the bar name gets cut off. Great tool! I'd like to be able to see the down to the week level for short term (quarterly) road-mapping as well.
In case it wasn't abundantly clear by the radio silence for the 22 months since this issue was closed, any comments will not be seen or responded to by Atlassian.
A feature was implemented that met the requirements originally outlined in this issue and the ticket was closed.
If it does not meet your needs as implemented (a perspective on this issue which I can appreciate) and you'd like to see action taken, either create a new suggestion-type issue which describes the desired feature or functionality that is lacking or, if there's an existing open issue that's similar enough (CONF-36103 perhaps?), add a comment and vote that issue up.