View Issue Details

IDProjectCategoryView StatusLast Update
0014088mantisbtbugtrackerpublic2014-12-22 08:24
Reportervboctor Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Target Version1.3.0-beta.1 
Summary0014088: Mantis 1.3.0 blocking issues
Description

This is a parent issues for blockers for 1.3.0 release. The bar for issues to become children of this issue is that they should be regressions compared to 1.2.x.

TagsNo tags attached.

Relationships

related to 0016444 closedvboctor Remove nusoap in favor of native php soap extension 
related to 0016446 closedvboctor Merge MantisConnect configs into MantisBT standard configs 
parent of 0014087 closedvboctor Installation script doesn't set the crypto_master_salt causing errors 
parent of 0014086 closeddregad Default administrator timezone to server timezone 
parent of 0014089 closedvboctor "Operation Successful" notifications are not centered 
parent of 0014090 closedvboctor Private are not rendered any differently than public notes 
parent of 0013691 closeddregad misspelled XHTML in admin/system_utils.php 
parent of 0014099 closeddregad Implement new message format for master branch at translatewiki 
parent of 0013304 closeddregad Error handler causes XML Parsing Errors 
parent of 0014119 closeddregad Use new MantisBT logo 
parent of 0014217 closedvboctor PHP error when attempting to save a filter 
parent of 0014398 closeddregad Support for PostgreSQL broken in 1.3 
parent of 0014756 closeddregad Sub project always fails at "check_selected" method when calling print_subproject_option_list 
parent of 0014760 closedgrangeway Bug Report Text Input Cannot Take Special Characters 
parent of 0014759 closeddregad Access Denied Page Has XML Parse Error 
parent of 0015446 closeddregad Using allowed html tags in text fields causes XML parse errors 
parent of 0015653 closeddregad APPLICATION ERROR 1303 when trying to reopen an issue 
parent of 0016020 closeddregad Port Fix of 0011684 to master branch 

Activities

atrol

atrol

2012-03-30 02:47

developer   ~0031567

Last edited: 2012-03-31 09:13

Regressions or not?
0011684:0027874
0012245

dhx

dhx

2012-03-31 10:13

reporter   ~0031585

0011684 can probably be considered a regression in 1.3.x because it looks like (from lots of negative feedback on the change) the change will only be possible if we completely rewrite custom field functionality in MantisBT.

I don't consider 0012245 a regression in 1.3.x. This was a navigation element that required JavaScript to work without a fallback mechanism.

dregad

dregad

2012-04-01 09:39

developer   ~0031586

Not sure if 0013304 really qualifies as "blocking" - but for sure it's annoying.

seyof

seyof

2013-02-05 12:14

reporter   ~0035034

it's boring and annoying

cisco

cisco

2013-05-12 22:35

reporter   ~0036835

done

grangeway

grangeway

2013-09-28 18:40

reporter   ~0038128

Removing sticky issue

rombert

rombert

2013-09-29 14:17

reporter   ~0038137

Reopening, not sure why Paul closed it...

vboctor

vboctor

2013-09-29 15:35

manager   ~0038141

@dergad, it would be great if you can update the team on the progress to address issues identified with "master" and when do you expect to merge back into master. It would be great if everyone is aware of where we are at with this.

vboctor

vboctor

2013-10-03 13:18

manager   ~0038188

I'm using "related to" to identify issues that would ideally be addressed, but are not required. These are lower priority than blocking, but higher priority that just issues with target version set to 1.3. We could switch to target version for these instead. Thoughts?

atrol

atrol

2013-10-03 14:46

developer   ~0038190

Do we need an issue "Mantis 1.3.0 blocking issues"?
We can set target version to 1.3.x, set severity to "blocking" and store a filter for it.

vboctor

vboctor

2013-10-03 16:16

manager   ~0038192

Works for me.

vboctor

vboctor

2013-10-09 00:12

manager   ~0038229

I've created "Major v1.3 Issues" public filter which shows issues targeted to 1.3.x release, that are not resolved, that has severity of "major" or higher. We should triage the issues showing up there.

I'm closing this issue in favor of the above filter.