Have updated to 1.6.2 and still have the same issue.
Here is some diagnostic info:
I have found out that owner_gp and owner_ms are defined in the table “tasks”
as the last two columns:
MariaDB [kanboard]> describe tasks;
+----------------------+--------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+----------------------+--------------+------+-----+---------+----------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| title | mediumtext | NO | | NULL | |
| description | mediumtext | YES | | NULL | |
| date_creation | bigint(20) | YES | | NULL | |
| date_completed | bigint(20) | YES | | NULL | |
| date_due | bigint(20) | YES | | NULL | |
| color_id | varchar(50) | YES | | NULL | |
| project_id | int(11) | NO | MUL | NULL | |
| column_id | int(11) | NO | MUL | NULL | |
| owner_id | int(11) | YES | | 0 | |
| position | int(11) | YES | | NULL | |
| score | int(11) | YES | | NULL | |
| is_active | tinyint(4) | YES | MUL | 1 | |
| category_id | int(11) | YES | | 0 | |
| creator_id | int(11) | YES | | 0 | |
| date_modification | int(11) | YES | | 0 | |
| reference | varchar(191) | YES | MUL | | |
| date_started | bigint(20) | YES | | NULL | |
| time_spent | float | YES | | 0 | |
| time_estimated | float | YES | | 0 | |
| swimlane_id | int(11) | NO | MUL | NULL | |
| date_moved | bigint(20) | YES | | NULL | |
| recurrence_status | int(11) | NO | | 0 | |
| recurrence_trigger | int(11) | NO | | 0 | |
| recurrence_factor | int(11) | NO | | 0 | |
| recurrence_timeframe | int(11) | NO | | 0 | |
| recurrence_basedate | int(11) | NO | | 0 | |
| recurrence_parent | int(11) | YES | | NULL | |
| recurrence_child | int(11) | YES | | NULL | |
| priority | int(11) | YES | | 0 | |
| external_provider | varchar(255) | YES | | NULL | |
| external_uri | varchar(255) | YES | | NULL | |
| date_board | int(11) | YES | | 0 | |
| owner_gp | int(11) | YES | | 0 | |
| owner_ms | int(11) | YES | | 0 | |
+----------------------+--------------+------+-----+---------+----------------+
35 rows in set (0.00 sec)
You can see that they are not defined as a "Key" in the 4th column.
I then check the table definition provide by kanboard under
/var/www/html/kanboard/app/Schema/Sql/mysql.sql
These two fields are not defined at all !
CREATE TABLE `tasks` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`title` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL,
`description` mediumtext COLLATE utf8mb4_unicode_ci,
`date_creation` bigint(20) DEFAULT NULL,
`date_completed` bigint(20) DEFAULT NULL,
`date_due` bigint(20) DEFAULT NULL,
`color_id` varchar(50) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
`project_id` int(11) NOT NULL,
`column_id` int(11) NOT NULL,
`owner_id` int(11) DEFAULT '0',
`position` int(11) DEFAULT NULL,
`score` int(11) DEFAULT NULL,
`is_active` tinyint(4) DEFAULT '1',
`category_id` int(11) DEFAULT '0',
`creator_id` int(11) DEFAULT '0',
`date_modification` int(11) DEFAULT '0',
`reference` varchar(191) COLLATE utf8mb4_unicode_ci DEFAULT '',
`date_started` bigint(20) DEFAULT NULL,
`time_spent` float DEFAULT '0',
`time_estimated` float DEFAULT '0',
`swimlane_id` int(11) NOT NULL,
`date_moved` bigint(20) DEFAULT NULL,
`recurrence_status` int(11) NOT NULL DEFAULT '0',
`recurrence_trigger` int(11) NOT NULL DEFAULT '0',
`recurrence_factor` int(11) NOT NULL DEFAULT '0',
`recurrence_timeframe` int(11) NOT NULL DEFAULT '0',
`recurrence_basedate` int(11) NOT NULL DEFAULT '0',
`recurrence_parent` int(11) DEFAULT NULL,
`recurrence_child` int(11) DEFAULT NULL,
`priority` int(11) DEFAULT '0',
`external_provider` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
`external_uri` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
PRIMARY KEY (`id`),
KEY `idx_task_active` (`is_active`),
KEY `column_id` (`column_id`),
KEY `tasks_reference_idx` (`reference`),
KEY `tasks_project_idx` (`project_id`),
KEY `tasks_swimlane_ibfk_1` (`swimlane_id`),
CONSTRAINT `tasks_ibfk_1` FOREIGN KEY (`project_id`) REFERENCES `projects` (`id`) ON DELETE CASCADE,
CONSTRAINT `tasks_ibfk_2` FOREIGN KEY (`column_id`) REFERENCES `columns` (`id`) ON DELETE CASCADE,
CONSTRAINT `tasks_swimlane_ibfk_1` FOREIGN KEY (`swimlane_id`) REFERENCES `swimlanes` (`id`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
Apparently they got added by some applications after the table is created.
I have also found from the database that in the table "project_activities", there are entries
relating to owner_gp (value 1) and owner_ms (value 0):
| 12323 | 1557993837 | task.update | 12 | 4 | 1221 | {"task_id":"1221","task":{"id":"1221","title":"Test of task number","description":"yet another test thing","date_creation":"1557993787","date_completed":null,"date_due":"0","color_id":"yellow","project_id":"4","column_id":"25","owner_id":"12","position":"3","score":"0","is_active":"1","category_id":"0","creator_id":"12","date_modification":"1557993836","reference":"","date_started":"0","time_spent":"0","time_estimated":"0","swimlane_id":"23","date_moved":"1557993787","recurrence_status":"0","recurrence_trigger":"0","recurrence_factor":"0","recurrence_timeframe":"0","recurrence_basedate":"0","recurrence_parent":null,"recurrence_child":null,"priority":"0","external_provider":null,"external_uri":null,"date_board":"1557964800","owner_gp":"1","owner_ms":"0","category_name":null,"swimlane_name":"Default swimlane","project_name":"test_production","column_title":"ELB\/Paperwork Complete","assignee_username":"c_h","assignee_name":"Chris Howe","creator_username":"c_h","creator_name":"Chris Howe","category_description":null,"column_position":"3","assigned_groupname":"Elec"},"changes":{"owner_gp":"1"}} |
Not exactly sure what they are used for.
The plugins I’m using are in the attached screenshot.
