mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #42867
[Bug 1694875] [NEW] Annotation field can be left empty when adding annotation
Public bug reported:
Mahara 16.10 and 17.04+
When you add an annotation block, you are supposed to be required to
provide an annotation in order to say why you align your portfolio with
a particular standard.
The "Annotation" field (no matter whether added via the SmartEvidence
map or as block) can be left empty though now when saving the block
configuration. It can't be added later on.
The field should not be left empty though as the annotation is a vital
aspect.
To replicate:
1. Add a collection with a SmartEvidence map.
2. Add an annotation via the SmartEvidence map.
Expected result: You can't save the configuration dialogue without typing an annotation.
Actual result: You can leave the field empty and save.
3. Add an annotation via the portfolio page.
Expected result: You can't save the configuration dialogue without typing an annotation.
Actual result: You can leave the field empty and save.
** Affects: mahara
Importance: High
Status: Confirmed
** Affects: mahara/16.10
Importance: High
Status: Confirmed
** Affects: mahara/17.04
Importance: High
Status: Confirmed
** Affects: mahara/17.10
Importance: High
Status: Confirmed
** Tags: regression
** Also affects: mahara/16.10
Importance: Undecided
Status: New
** Also affects: mahara/17.04
Importance: Undecided
Status: New
** Also affects: mahara/17.10
Importance: High
Status: Confirmed
** Changed in: mahara/17.04
Status: New => Confirmed
** Changed in: mahara/16.10
Status: New => Confirmed
** Changed in: mahara/16.10
Importance: Undecided => High
** Changed in: mahara/17.04
Importance: Undecided => High
** Changed in: mahara/16.10
Milestone: None => 16.10.5
** Changed in: mahara/17.04
Milestone: None => 17.04.3
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1694875
Title:
Annotation field can be left empty when adding annotation
Status in Mahara:
Confirmed
Status in Mahara 16.10 series:
Confirmed
Status in Mahara 17.04 series:
Confirmed
Status in Mahara 17.10 series:
Confirmed
Bug description:
Mahara 16.10 and 17.04+
When you add an annotation block, you are supposed to be required to
provide an annotation in order to say why you align your portfolio
with a particular standard.
The "Annotation" field (no matter whether added via the SmartEvidence
map or as block) can be left empty though now when saving the block
configuration. It can't be added later on.
The field should not be left empty though as the annotation is a vital
aspect.
To replicate:
1. Add a collection with a SmartEvidence map.
2. Add an annotation via the SmartEvidence map.
Expected result: You can't save the configuration dialogue without typing an annotation.
Actual result: You can leave the field empty and save.
3. Add an annotation via the portfolio page.
Expected result: You can't save the configuration dialogue without typing an annotation.
Actual result: You can leave the field empty and save.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1694875/+subscriptions
Follow ups
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Robert Lyon, 2017-10-30
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Niranjan, 2017-09-14
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Robert Lyon, 2017-09-11
-
[Bug 1694875] A change has been merged
From: Mahara Bot, 2017-09-10
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Cecilia Vela Gurovic, 2017-09-10
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Robert Lyon, 2017-09-07
-
[Bug 1694875] A change has been merged
From: Mahara Bot, 2017-09-07
-
[Bug 1694875] A change has been merged
From: Mahara Bot, 2017-09-07
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-09-07
-
[Bug 1694875] A change has been merged
From: Mahara Bot, 2017-09-07
-
[Bug 1694875] A change has been merged
From: Mahara Bot, 2017-09-07
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Robert Lyon, 2017-09-07
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-09-07
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-09-05
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-09-04
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-09-04
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-09-04
-
[Bug 1694875] A change has been merged
From: Mahara Bot, 2017-09-04
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Robert Lyon, 2017-09-04
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Kristina Hoeppner, 2017-07-20
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-07-06
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-06-25
-
[Bug 1694875] A patch has been submitted for review
From: Mahara Bot, 2017-06-22
-
[Bug 1694875] Re: Annotation field can be left empty when adding annotation
From: Pramith Dayananda, 2017-06-19