Skip to main content

Sharing #featurerequest or ideas for fBoards/fRoadmap:

  • Share Tasks or Share Stages or Share Whole fBoard with other fBoard instances located in our Wordpress instance or outside our WP instance hosting.

    Note: in the last case scenario (share fBoard outside our WP instance) if external sharing is enabled "fBoard Taker" must deal somehow with users assigned details - probably they cannot be mirrored from "fBoard Giver" just to keep users details privacy etc**.**

    Case scenario details:

    If we are dealing with Stakeholders/Agency Clients we could have possibility to outsource and share some Tasks/Stages/fBoards externally (fBoard Native Integration option with other external fBoard?).

    External Stakeholders/Clients could have a separate fBoard (their own instance on their hosting) where automatically we/they could Pin external Tasks/Stages/fBoards (if they have role/permission access to it or if they are invited and if they Accept/Reject such a incoming request).

    External fBoard admins/users with this permission (users with viewer only role excluded) could accept incoming workload (in their fBoard/WP instance) but also we (in our fBoard/WP instance) incoming Tasks/Stages/Boards or reject them - if a user has such a role/permission: like admin in that fBoards).

    This whole process could be done in the fBoard Manager settings where admin could have the option to provision sharing fBoards access within his own WP instance but also share access with External WP website (who have fBoards license)

    Example:

    fBoards Admins/Managers (users with Manager/fBoard Owner role) could Feed or Push or Mirror (view only permission): Tasks, Stages, Boards and Accept or Reject or even Block (by default) possibility to access any other Wordpress fBoard instances (internal/external).

  • Add to Advanced Filter option to display: Archived tasks - easy way to show/access archived tasks (Deleted tasks filter would be an option only if tasks would go to a Trash bin / Deleted Tasks Group).

  • Archived tasks could completly dissaper from our Stages list (but users sould be able somehow to view them ex. by filter) or be greyed-out but still be visible on the Stage cards. Or... a separate idea is to implement: "ArchivedTasks group/sections" (see below point) could be shown under the Stage with "ActiveTask group". fBoard User (viewer only role excluded) should be able to unarchived his own tasks but also all task (if he has the role/permission access granted by admin).

  • Each Stage card should be divided into a tasks groups/sections (within those groups/sections users could see task as of now) - those visual groups/sections are:

    • 1st/top group: Active Tasks
    • 2nd group: Active Sequncial Tasks
    • 3rd group: Completed Tasks
    • 4th group: Draft/Archived Tasks
    • 5th/bottom group: Deleted Tasks (tasks stays 10 days once deleted in this Group unless Deleted Tasks are permanently but deleted from this Group.

    Note: User with Admin Role could sepcify visibility of those Tasks Group for other Users.

    Note2: Groups like Archived/Deleted tasks could be collapsed by default (save some space) but the rest groups could be expanded (user specific view)

  • Admin or a user who is creating tasks could hide tasks (task visibility option). Example: the place for Draft tasks could be created either in a separate Stage (Draft bin) with such a limited visibility to other users or Draft tasks could be directly displayed in a separate Group: Draft Tasks (displayed under the Group of Active Task but above Group Archived Task). Users could select visibility option for a draft task (his own) in the Stage tasks list.

    While creating a new task (if such a role/premission is assigned to current logged user) a person could decide who can see this task (options for tasks visibility on a Stage card could be: Admins only, Everybody in this fBoard, Assigned person, TasksAuthor/Owner or Allow to share task visibility Externally or even mixed/selected. Note: by default task visibility to other users could be marked as: Everybody can see this task in this fBoard, but without External Sharing). Default tasks visibility option could be setup by fBoard Admin.

  • Implement Roles/Granual Permissions for users/users group where admin could decide which Permission is assigned to Users Group or Individual User

  • User with fBoard Admin Role should be able to lock:

    • fBoard design in fBoard settings so only admins could change colors, Stages orders, labels, background, which view users are able to even view/select, etc
    • decide if "Boardmembers list item/icon" or any other item/icon from top header is visible to fBoards users at all (especially if we will have external users invited to this fBoard)

  • Login to fBoards with magic link only for External Guests (Temporary One Time Access token could be send via email to invited external user). \ Prerequisite: WP Admin (or fBoard admin if have such a role for inviting users) need to create such a login/user in WP admin console > Users. \ fBoards admin could decide also how long this user could access fBoard via magic link (1 day, 7 days, until...date, limited usage: x times, limited concurrent/active sessions to: x users)

  • Consider option: "tasks completion squence" to appear on a fBoard cards (Tasks dependency could be configured by each user (Own Task). Task who has master/upper in sequence tasks not completed, could be GreyedOut to everyone or/and even not visible to all users but only to the task creator+user with admin role).

    Tasks creators (author role) could configure task sequence with own text code - example I create Master Task with unique symbol GD (or autogenerated): therefore this task has unique identifier gd00, and next dependend tasks sequence needs to have assigned ID: gd01, gd02... (this could be automated without typing manually those IDs to sequenced tasks - drag and drop change sequence tasks order).

    Also Admin or Author could specify the visibility option for "tasks who are depended from not completed Master task". When master/previous tasks are not completed they should be: Visible to Everyone or Visible to the Creator+Assigned User and/or Greyout/Normal Color).

    Dependend tasks should be also marked with a special icon (\<!>) and the icon could be linked to Master/Previous or Slave/Next task so confused user could click it and see which tasks it is linked to.

    Note: if task is moved between stages user still could click the link to previous or next task when he hover mouse on the sequence task icon then it could be displayed dotted lines to all tasks in this squence).

    Sequence tasks could give all users the clearance what Tasks should be completed first and what is the sequence.

    *We are talking here about Tasks Sequence Completion Order which is not the same as manual Sorting tasks order (drag/drop) on the Stage card.

  • If current filter settings are Global for each fBoard then it would be good to specify if this filter is Reset each time a user access/change fBoard or if filter should be saved to Admin selected filter view or User selected filter view.

    Filter options could be: default filter or user specific/custom and it would help users to move around especially if then want to see (everytime they are accessing fBoards) only his own tasks with their last Filter settings.

    Example: If a user apply a filter by tag: called Important (Red Color) then this filter should be applied for him for the next session but only for him. \ Dont forget about: pre defined filters (Default view, User specific aka Custom View) and reset filters option).

  • Implement option to Pin tasks do Dashboard for a Current Day. \ So let`s say that a user will start working on his tasks in different fBoards. User should be able to select tasks for Today (if user pin a tasks to Today Tasks list on dashboard and he wont complete them then the next day Dashboard Today Tasks list will be empty (Getting Things Done rulez)

    Note: fBoard admin (or a specific: Manager/Supervisor role) could see on a Dashboard also all users list adn their Today Tasks List for each user ;)

  • Able to choose for Front-end view a custom subdomain: CustomNameLikeSlug.domain.com rather then domain.com/projects# URL in order to access fRoadmap of even public fBoards (if implemented).

    Warning: additional note should be presented to fBoard admin that this require a specific DNS Resoure Record configuration *.domain.com - catch all subdomains - specific CNAME and also entry in .htaccess rule (manual or automatic) should be added.

    Warning2: if front-end view is enabled with login form then it is easy to discover link to real wp-admin form - it would be good to think how avoid discover wp-admin custom slug if someone use a separate plugin to "hide" domain.com/custom_adminSlug like: WPS HIDE LOGIN

  • Option to protect with Custom Password the Front-end view url + ability to select settings for crowlers: Index, NoIndex, Follow, NoFollow this page by crawlers + ability to select it this page is added to Sitemap.xml:\ <meta name="robots" content="``noindex, nofollow``" />

  • For the future... (currently there might be too many feature changes to keep the update) you could provide a library to manuals/instructions/short videos how to deal with fBoards

  • Consider Integration with apps like: ToDo (Microsoft), Tasks (Google) and via webhooks

  • Possibility to store attachments from Tasks in External repositories like: GoogleDrive, OneDrive (if fBoard admin enaled such a integration for that fBoard etc).