Sigmah Issue Tracker - Issues

0000564: Wrong character set on new user creation email

Mon, 17 Jun 2013 12:53:55 +0200

On the 1.2-rc3 beta test server (demo.sigmah.org/1.2-rc3), while I've runned test http://code.google.com/p/sigma-h/wiki/TestScenario4UserSessionRight#USR8, [^] I've received an email with this subject: "=?ANSI_X3.4-1968?Q?Acc=3Fs_=3F_l'application_Sigmah?=".

Looks like a character set problem...

0000552: Advanced logframe management privileges

Sat, 15 Jun 2013 14:41:56 +0200

Currently, if a user has right to edit a project, he has also the right to manage the logical framework: create/delete/modify content in it.

A more advanced behavior would add 2 global privileges:
- VIEW_LOGFRAME for viewing the logframe sub-tab
- EDIT_LOGFRAME for creating/modifying/deleting objectives, expected results, activities, hypothesis or linking/unlinking indicators to the logframe

0000388: Export to Excel

Fri, 14 Jun 2013 12:37:35 +0200

Users have expressed the need to be able to export each screen of the application under a format usable with MS Excel (and potentially with LibreOffice Calc as well). That way, they will be able to build their tools, and their own analysis our of the information stored into Sigmah.

More precisely, this means having a Excel export button on each of the following screens or components :
- project list (on the main Dashboard and on the orgunit Overview)
- indicators management sub-tab
- indicators entry
- logical framework (it will implement then issue 0000110)

This feature is a simpler version of issue 0000213 Custom exports.
The implementation of this feature should take into account the future implementation of the Custom exports.

A proposal for a very detailled version description of this feature is given in the attached User Report URL.

0000563: Message error when loading project with empty category value

Thu, 13 Jun 2013 11:36:31 +0200

In a question element linked to a category, if a value is given to the question element in a project and it is removed, an error message occurs when the projects are loaded in the dashboard.

0000167: Revise Amendments system behavior

Wed, 12 Jun 2013 16:44:21 +0200

Amendments should be renamed "Project core version".

Project core versions are a way to keep track of modifications of the core logic of intervention of the project.
The logic of intervention consists of:
- the logical framework
- all indicators attached to the logical framework (all their characteristics (name, target value...) except their value)
- start and end dates of the project
- planned budget field (or more precisely the budget sub-field used as ratio basis for budget progress computation)
- any indicator set as "part of the core logic of intervention" of the project
- any activity set as "part of the core logic of intervention" of the project
- any field set as "part of the core logic of intervention" of the project in the model

Project core versions visualization
In the top right corner project page (on the right of the banner), a box is set to manipulate Project core versions.
A drop-down list will allow to set under which Project core versions should the project be seen (by default, the project will be seen as in the last version).
In the drop-down list, all the available Project core versions will be listed like:
n°0 - 01/12/2012 - Initial version
n°1 - 14/01/2013 - Revision of the number of beneficiaries
n°2 - open version

On the right of this drop-down list, a button "Display" is available to change the project and show it with the value of all content of the logic of the project as freezed in the selected Project core version.
Below the drop-down list, a button "See version summary" will open a popup which will list all the modifcations between the selected version and its previous version. In this popup the version of project core used as reference for comparison can be selected among all the previous versions to the one selected initially.
Below this last drop-down list, a textfield "Project core version title" will be available to update the selected version title.
The graphical design of this box should be revised to reply to the needs expressed by this draft graphical design.

Each information which has been modified since the initial version will be highlighted through a small mark (an exclamation mark?) to inform the user that some changes have been made on it in a Project core version . By clicking on this small mark, a popup will open listing all the modifications made in each of the Project core version (with the number, date and title of the modification).

If it is a past version which has been selected, when the user will navigate inside the project, he will see for each modified information the information as set in the version, as well as the present version (in a different color?) for comparison. Of course, the small mark will also available to see all the Project core versions made on this information.

Modifications workflow
When a project is created, the version #0 is open for modification.
A user with the required global privilege can lock a Project core version so that all information linked to it are no more open to modification.
When a Project core version is locked, it can be validated by a user having another required global privilege, or unlocked by a user having the "Lock Modification" global privilege.
When a user validates a Project core version, the user can enter a title for the version.
When the last Project core version is validated and a user try to modify an information of the Project core, he will get a popup informing him:
- if this user has the "Create new Project core version" global privilege: "By modifying this information, you will create a new Project Core version. Do you want to continue?"
- if this user doesn't have this global privilege: "This information is part of the Project core, and the current version of the project core is not open for modification. Ask someone with the required privilege to open the project core for modification". <= this message will also be displayed if the project core version is locked.

0000463: Problem between local date and stored date in the database

Wed, 12 Jun 2013 15:01:29 +0200

When an user use the software in a place with a different timezone than the database and if this user change the value of a date field, the value showed after can be inconsistent relatively to the date previously entered.
This problem is occuring only on some date field as the start date and the end date of a project.

0000562: Make the maximum size of uploaded files configurable through the properties file

Wed, 12 Jun 2013 14:53:14 +0200

Move the specification of the maximum size of uploaded files into the properties file of the application.

0000491: Report field not working if attached to project Details sub-tab

Wed, 12 Jun 2013 13:51:14 +0200

In a project model, if a report field is attached to the project Details sub-tab:
- it won't be possible to create the report from the button "New" in the Reports & documents sub-tab
- once the report created from the Details sub-tab, it won't be listed in the Reports & documents sub-tab, and cannot be opened neither from the Details sub-tab

0000409: Delete profiles and privacy groups

Wed, 12 Jun 2013 10:51:59 +0200

As requested in attached user report, a feature to delete profiles and privacy groups is missing.
This feature should be developed with a "Delete" button in the toolbar above the list of profiles, and another one above the list of privacy groups.

When requesting a deletion, the user will get a warning message informing him of the usage of the profiles/privacy groups:
- when attempting to delete a profile, he will get informed of all users still linked to this profile if any
- when attempting to delete a privacy group, he will get informed of all project/orgunit models' fields and profiles linked to this privacy group if any

0000488: Possible to modify an orgunit without orgunit modification global privilege

Tue, 11 Jun 2013 16:58:54 +0200

Even if a user doesn't have the global privilege "Manage organizational units", he will be able to modify most of the attributes of orgunit.
A user without this privilege shouldn't be able to modify anything in an orgunit.

0000548: Budget field always editable

Tue, 11 Jun 2013 15:58:00 +0200

Currently, the budget field is always editable when visible.
If view right are only given on the budget field, it should not be editable.

0000502: Notification window too small for error message "Direct data entry for this indicator"

Tue, 11 Jun 2013 15:55:20 +0200

On the Indicator Data Entry sub-tab, when the error message "Direct data entry for this indicator is disabled; you can enter results in these sources of indicator data" is poped up, it is too big for the notification window and cannot be read completely.
The notification window should be bigger for this message in order to let it appear completely.

0000544: Calendar empty if user timezone different from server timezone

Tue, 11 Jun 2013 11:01:45 +0200

The calendar is totally empty if the user timezone is different from the server timezone.

0000557: Events disappear

Tue, 11 Jun 2013 10:51:28 +0200

When an event is added, it automatically disappears when the sub-tab is changed and when the project is closed.

0000559: Right click behavior should have all classic options

Sun, 09 Jun 2013 05:13:54 +0200

When you highlight text from a field and do a right click to copy it or when you want to do a right click to correct typo mistake, the only options given is "show history"without the classic options.

0000458: Assigning an OrgUnit to a test project makes it visible to all

Mon, 03 Jun 2013 15:13:34 +0200

On a test project, if a user changes the default organizational unit attached to it, the test project will be become visible to all and not only to him.

0000099: Funding source Budget part percentage not udpated on total budget change

Mon, 03 Jun 2013 14:56:02 +0200

If the total budget of a project is changed, the percentage of each of its funding source in this total budget is not updated.
Those percentages should be computed and updated.

0000558: Deleted versions of files should no more be available

Mon, 03 Jun 2013 14:44:21 +0200

There is a mean to download a deleted version of a file attached to files list field.
Deleted versions of files should no more be available.

0000546: User edition popup doesn't load user invitation language and password

Mon, 03 Jun 2013 14:34:51 +0200

When you want to edit an user (e.g. give him new profiles) you always have to change the invitation language (which isn't properly loaded).
Much more serious, since the password is neither loaded, if the user clicks on save without entering the password, it will empty the password... and allow to enter the application just with an email without entering any password!

0000504: Increase project code available length

Mon, 03 Jun 2013 14:23:38 +0200

A user reported (see attached user report url) the need to have a longer field available length for project code
The maximum length should be increased to 50 characters to be sure not to have the same feature request anymore.

0000500: Export to Open Document spreadsheet format not working

Mon, 03 Jun 2013 14:20:15 +0200

In v1.2-rc1, both on the Global export and the Project synthesis export, the exportation fails if the *.ods format is selected.

This bug might be linked with the execution of the odftoolkit library on a Windows 7 environment. See full trace in Additional information.

0000495: Remove suggestion to add a reminder when attaching a file

Mon, 03 Jun 2013 14:18:03 +0200

In almost all cases, user click on "No" when Sigmah suggests to them to add a reminder after attaching a file. Moreover, this feature creates a bug when a file is attached to an orgunit, because no reminder can be set for an orgunit.
This feature should be removed.

0000378: Technical error on report creation

Mon, 03 Jun 2013 14:06:03 +0200

A user from the French Red Cross has reported a technical error she get always while creating a report. She's not able anymore to create on her accounts on Sigmah Central.

See attached log from the server, and attached user report url for more information.

0000499: No empty column for files list field in global export

Mon, 27 May 2013 16:54:26 +0200

In v1.2-rc1 global exports, files list field are represented by an empty column in the Excel exported file.
Until issue 0000484 is developed, there should be no column in global export for files list fields.

0000498: Global export should not contain deleted and test projects

Mon, 27 May 2013 16:54:26 +0200

In v1.2-rc1, global exports contain deleted and test projects. They shouldn't be exported.
As a consequence, draft project models should not appear as tabs in the exported Excel file.