-
Notifications
You must be signed in to change notification settings - Fork 729
Comparing changes
Open a pull request
base repository: mantisbt/mantisbt
base: 22f830c
head repository: mantisbt/mantisbt
compare: ae8be02
- 13 commits
- 15 files changed
- 1 contributor
Commits on Dec 15, 2011
-
Correct display custom status in cross-project relationships
In the bug relationships section in view.php, the target bug's status was incorrectly displayed as "@x@" (where X is the status_enum id) if the following conditions were true: - the target bug is in a different project - it is a custom status This commit fixes the behavior, and displays the corresponding enum element's language string. 2 new parameters have been added to function get_enum_element(): user and project id (defaulted to null to preserve existing behavior). These parameters are passed on to config_get() call, allowing to specify the context for retrieving the enum element. The call to get_enum_element() in function relationship_get_details() has been altered to specify the target bug's project id. Fixes #11323
Configuration menu - View commit details
-
Copy full SHA for f33c0f8 - Browse repository at this point
Copy the full SHA f33c0f8View commit details -
Additional fixes for display of custom status
Resolves additional display issues of custom status cross-project, similar to what was fixed in 324dbb4681255b7a1fa4cc309ab8742f028dbf43. These can occur when "All Projects" is selected and one or more projects have custom statuses not defined globally, in the following pages: - View Issues - Change Log - Roadmap - Sponsorship Affects #11323
Configuration menu - View commit details
-
Copy full SHA for 02fed50 - Browse repository at this point
Copy the full SHA 02fed50View commit details -
- fix whitespace errors - align to coding guidelines - moved variable initialization out of for loop
Configuration menu - View commit details
-
Copy full SHA for 52dbd32 - Browse repository at this point
Copy the full SHA 52dbd32View commit details -
Fix cross-project display of custom status colors
When a custom status is defined in a different project, its custom color was not used (displayed white) in the following cases - view issue details page, relationship - View Issues - My View - Sponsorship - Bug group action list Fixes #13682
Configuration menu - View commit details
-
Copy full SHA for 7dfab37 - Browse repository at this point
Copy the full SHA 7dfab37View commit details
Commits on Jan 1, 2012
-
Fix cross-project display of custom resolution codes
When a custom resolution is defined in a different project, its code was displayed as @x@ instead of the corresponding string in the resolution column, as well as when hovering over the status in the view issues page. Fixes #13707
Configuration menu - View commit details
-
Copy full SHA for b764401 - Browse repository at this point
Copy the full SHA b764401View commit details
Commits on Jan 13, 2012
-
Fix cross-project display of custom severity and priority
When a custom severity is defined in a different project, its code was displayed as @x@ instead of the corresponding string in the severity column on the View Issues page. The same problem applied to custom priorities Fixes #13718
Configuration menu - View commit details
-
Copy full SHA for 8538a5d - Browse repository at this point
Copy the full SHA 8538a5dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 735506c - Browse repository at this point
Copy the full SHA 735506cView commit details -
Fix custom enum types across projects in exports
The CSV and Excel exports, as well as printing a report to Word now properly handle custom enums when dealing with bugs from different projects. Fixes #13728
Configuration menu - View commit details
-
Copy full SHA for a39a948 - Browse repository at this point
Copy the full SHA a39a948View commit details
Commits on Jan 30, 2012
-
Fix use of undefined $t_bug variable instead of $p_bug
Copy/paste error introduced in 735506c Affects #11323
Configuration menu - View commit details
-
Copy full SHA for 8d115d9 - Browse repository at this point
Copy the full SHA 8d115d9View commit details
Commits on Feb 28, 2012
-
Merge branch 'fix-11323-cross-proj-rel'
Conflicts: excel_xml_export.php
4Configuration menu - View commit details
-
Copy full SHA for 9a069ce - Browse repository at this point
Copy the full SHA 9a069ceView commit details -
Extra column in csv export when sponsorship_total >= 1000
Bug introduced by commit a786f9b. Due to the use of number_format() function with default parameters, PHP outputs the sponsorship amount formatted with ',' as a thousands separator, which also happens to be MantisBT's default csv separator. Since the fields are not escaped, this causes an extra column to be generated. Call to number_format() was removed, as it makes more sense to output raw data in csv exports. Fixes #13958
Configuration menu - View commit details
-
Copy full SHA for 0791a49 - Browse repository at this point
Copy the full SHA 0791a49View commit details -
Add function to handle Excel formatting of sponsorship
When exporting issues in Excel format a fatal error is thrown if the export includes sponsorship totals. This is due to a missing excel_format_sponsorship_total() function. Fixes #13959
Configuration menu - View commit details
-
Copy full SHA for 087b1fc - Browse repository at this point
Copy the full SHA 087b1fcView commit details -
Fix bug in access_has_bug_level() for private issues
When private_bug_threshold is defined as an array instead of a single access level, e.g. array(0=>40, 1=>70, 2=>90) to prevent developers from seeing private bugs while granting that privilege to updaters, access_has_bug_level() incorrectly returned true. The consequence is that unwanted access to Private bugs was granted to users who are allowed to view them, e.g. allowing them to delete or perform other restricted actions. Fixes #10124
Configuration menu - View commit details
-
Copy full SHA for ae8be02 - Browse repository at this point
Copy the full SHA ae8be02View commit details
There are no files selected for viewing