I would like to develop/contribute an entirely new feature, to visualize roadmaps or development progress. This is a call for a request (CFF) if this is in your interest and has the potential to be merged.
In every project (which uses Jira), project planning is a big question. There are robust tools out there since centuries, like Gantt charts. Many plugins for Jira exists, which bring this functionality. In many companies, Jira is a centrally managed software and adding a plugin, even is they are for free, is not an option ... because of security or not enough capacity to maintain them. This feature should enable individuals to quickly visualize epics, stories, etc .over time and additionally provide quick editing features.
The value for the user would be to not waiting for central IT dept. and being instantaneously enabled to visualize or mass edit tickets.
Users with the highest interest might be freelancers, consultants or any other people who frequently change projects and can't wait for long-running application and installation processes. Also, "regular" Jira user might use it when for some reason they are not able to get other Jira plugins centrally installed.
(using MoSCoW prioritization scheme, https://en.wikipedia.org/wiki/MoSCoW_method)
This feature looks to be pretty interesting and definitely you can go ahead with it. But I would like to know few more details based on which I had to plan for something:
For you to work on this feature, I would suggest you to use a separate branch itself having base as develop. Once entire development and testing is done that can be merged with develop
thank you for your feedback. Regarding your questions and comments...
In terms of merging back to your develop branch and release ...
I'm a big fan of smaller (intermediate) releases, which reflect a Minimum Viable Feature (MVF).
It would be great if e.g. I start on a "read-only" view first and release this as "beta" feature. This could be possible within 2-3 weeks maybe. And we would be able to gather feedback. On top of that, the next release could include some custom filters OR some editing options. etc. What do you think about that approach?
sure, that shouldn't be a problem.
hi @nitram509 , Hope everything is good. I would like to let you know that their were lots of changes in repository and I would suggest you to have your branch updated always so that you will not have any issue using the existing services. Their were lots of fixes from the time you had forked the repository and so would request you to use an updated version before continue with your activity.
thanks for letting me know - I will do.
I have some little progress. I managed to add a new menu item " Roadmap View" and started to insert jQery Gantt Editor (from TWProject). It's quite a challange to rewrite the un-modularized jQuery code and make it compile in a React context.
So good new, I was able to include the sources and make the JA compile ... but still working on showing something ;)
Unfortunately, I only managed to make it compile by altering package.js -- to reduce the compiler severity level. I'm new to React, so still need to learn more about it's lifecycle.
"no-unused-vars": "warn", "no-unreachable": "warn", "eqeqeq": "warn",
Just wanna share a little progress ... 1 picture say more than 1000 words ;) The first time something useful is loaded ;) Unfortunately, the splitter does not work yet ;)
Another dev snapshot ... got the jQery Gantt Editor almost completely working Commit check sum is 8766bab3761b2f81bfa31095a3a72a76bd307ac6
Development notes ...
I dropped the former approach of using jQuery Gantt Editor fo these reasons
Currently looks like this ... (the button 'load tickets' already works ;) )
Development update: due to some private reasons, I want to spend my remaining spare time this year on other projects. I definitely plan to continue this feature, but for now: paused.
Sorry to spoil the party, I'm just wondering. There are gant charts in next gen Jira projects. They work excellent. I suppose not everybody uses Jira cloud. A lot of legacy projects use Jira locally. Maybe for them it makes sense.
Hi Adrian, thanks for pointing that out. Indeed there are many plugins for Jira on-premises available, as well as the one you mentioned in Jira cloud offerings. Nevertheless, I'm regularly facing the situation, where such can't be used and hence my motivation was to start such an alternative solution. Unfortunately, my spare time for coding is limited.
@nitram509 - Are you still using Jira Assistant? If yes, what is your plan on this item? Are you planning to continue on this in any near future?
If not please feel free to close this issue as won't fix. I am trying to fix/close all the possible issues currently in tracker. So just thought of checking.
I'm no more working on this ... since we switched to the newer Jira cloud offering and my use case is gone.