Future Enhancements Ideas

[cgaspard]

If you have an idea, and want to share it, please post here, and I'll keep a running list of items I will be working on.

New features that will be implemented:

1. Link to mantis projects from the Kanban
2. Due date field
3. Enforce required fields
4. Support for all custom fields (See issue #31)
5. User color customization (See issue #34)
6. Check for null in task list (See issue #30)

Done in "dev" branch (see demo server)

1. Gravatar integration
2. Display issue history in history tab
3. History Tab (requires mantis 1.3)
4. Task or SubTasks (requires mantis 1.3)
5. Theme support
6. Added Severity & Resolution fields

Ideas for future:

1. Allow for a list of issues to be hidden
2. Additional fields / Custom Fields Display
3. Monitoring for issues and / or projects
4. Swim Lanes (By user and / or custom field)

Completed Items:

1. Link to mantis for issues and projects
2. Allow links to automatically open items (http://mantis.com/mantiskanban/index.html?issue=1234)
3. Sub-Project Support - completed but in testing

[rafaeladolfo]

I have a few ideas..

1. Integration with gravatar - to show the gravatar picture inside the cards (replacing the initials) (this could be a parameter, if true = pics, else = initials).-I`ll try to work on this on my forked project
2. Subtasks - It would be GREAT to have this, We could see a list of subtasks (using check boxes), it would save the list in a custom field.
3. Show due dates.
4. Enable to use the 'monitoring' function, to add people to monitor some issue.(if mantis could support multiple handler's to some issue it would be the perfect solution, but monitoring can be useful also)

[cgaspard]

I actually started the gravatar integration a while back. I have some code that is incomplete in the Kanban already. I'll add it to my list for completion later.

For #2, #3 & #4, Are these something supported in Mantis? I haven't planned on extending the functionality of mantis itself. Only give a better presentation for what is available. If the native functionalty is there, I'll consider adding it.

[rafaeladolfo]

@cgaspard for #2 I need to figure if it's possible by using custom fields, this is not a native functionality.

For #3 Due dates are available in mantis.

For #4 Monitoring is also supported.(SS:view.php)

[cgaspard]

For subtasks lists, it makes sense to support it through custom fields. I'll think about this for a bit, and let you know if I can build it.

[rafaeladolfo]

Great! more ideas

1. And what do you think about using ctrl+enter to add new notes?
2. And this is for think.. Is there any way to implement @mention? Like having a panel with recent activities in a project? (showing history from all stories) So you can see if someone has mentioned your name in some card (storie) (like a discussion). And, in order to see the mentions, you could query every notes with @ character in it.. I've built the query to you to take a look..

this one will return all notes that someone has @mentioned someone..very good for news awareness

SELECT A.BUG_ID,B.realname, c.summary, e.note FROM mantis.mantis_bug_history_table a, mantis.mantis_user_table b, mantis.mantis_bug_table c, mantis.mantis_bugnote_table d, mantis.mantis_bugnote_text_table e where a.user_id = b.id and a.bug_id = c.id and from_unixtime(a.date_modified) > NOW() - INTERVAL 30 DAY #last 30 days, only a suggestion AND C.project_id = 3 #the project ID AND A.TYPE = 2 #type = 2 > notes and A.bug_id = d.bug_id and d.bugnote_text_id = e.id and d.date_submitted = a.date_modified and e.note like '%@%' #only get notes with @mention order by a.date_modified desc;

You could display the information like this: B.realname || ' added note on ' || A.BUG_ID || '-' || c.summary || ':' || e.note 'rfa1989 added note on 26 - Future Enhancements Ideas: @cgaspard Take a look at this.

If you wish, you and select any kind of history notification changing the a.type value

Am I going to far? What do you think?

[cgaspard]

For 1. do you mean instead of having to click the add button? If so, that definitely makes sense.

For 2, I don't want to make any changes to the Mantis code. If this feature was implemented as a Mantis Connect API, I would be willing to hook into it.

Also, Just wanted to mention I built the task list for issues into my latest version. "dev" branch in github. I have a working version on the demo site now. I won't be able to release until mantis 1.3. It requires a custom field defined, and a config.js param that will store the task list. Mantis 1.2 custom fields as strings have a limit of 255 chars, so I the current version I had to disable the feature. In the newer Mantis, there is a textarea custom field type that is store as a text field and has a much larger limit suitable for storing the task list.

[rafaeladolfo]

1. That's exactly what I meant! It would be much more faster for adding notes having this shortcut.
2. So, I guess this feature should not be considered, there's nothing in mantis code similar to this!

I've just checked the demo site! The task list is very nice!!!! Let's wait for 1.3 for this feature..

[rafaeladolfo]

There is one more thing

Plus 1 vote for additional fields (and obligatory fields such as root cause, before close a issue)

Allow to add relationship to issues inside kanban, and display the child/parent/related issue status as well

[stormbom]

Vertical swim lanes would be very nice, if feasible!

Eg in our Mantis setup, we have set up a custom field KanbanState analogously to the ScrumBucket one, with Work-In-Progress representing the items currently being worked on - if that could be subdivided vertically using a custom field or perhaps category, that would be swell!

For example:

---

WORK-IN-PROGRESS WiP-Category1 [Item 1]

[Item 2]

WiP-Category2 [Item 3]

[Item 4]

---

Edit: okay, formatting was a bit screwed up, but hopefully the idea got through :)

[cgaspard]

@stormbom ,

I've been toying with the idea of swim lanes, but I was planning on basing them on users not statuses or custom fields.

I'll think it over and add this to the suggestions.

[stormbom]

Swimlanes by user would be quite nice as well!

In our own Mantis Kanban setup we made a small change to allow configuring the background color for the Kanban cards based on category, in order to make them more visually distinct, eg.

Kanban.CategoryBackground = { "Deliverable" : "#bae", "Improvement" : "#abe", "Issue" : "#eac", "Task" : "#dea", "Project" : "#bea" }

(+ a GetCategoryBackground function analogous to the GetCategoryIcon one, and setting the background-color style attribute for storyContainerDiv). Perhaps that could be incorporated as well?

[filozofer]

I'm currently trying your awesome project, thanx to you !

I've seen two things that need to be fix for our mantis to be correctly supported as you can see in the picture below:

• We have an extremly long list of projects, make it impossible to choose some of them because the list overlay the screen.
• We have many custom status and as you can see they are not translate by their name. Just got "@60@" for name rather than "Deliver" (custom choice).

Oh and by the way, we have configured mantis to get an email each time a ticket is update, but when we drag a ticket in your dashboard to the same list he is already we've got an email anyway (even if it's not a real change).

Good job !

[ronlinet]

Reuse mantis authentication. To to access a kanban board user have to go through the authentication process what ever he is logged in the tracking system or not. Wouldn't it be more convenient to reuse the mantis authentication mechanism and let the user in if he is already authenticated ?