Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0028039ModulesTax Report Launcherpublic2014-10-31 10:312015-02-26 14:07
Reportermaite 
Assigned Tofsoto82 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket
OBNetwork customer
Regression introduced in release
Summary0028039: Year information should be considered from period's information instead of name set in Year window
DescriptionYear information should be considered from period's information instead of name set in Year window
Steps To Reproduce1. Access Fiscal Calendar window and Year tab and modify name of "2015" year to set, for example, "Año1"
2. Access Tax Report Launcher window, select your "Año1" to run any AEAT report and realize that information exported to file is "Año1" instead of "2015"
Proposed Solutionyear exported to file should be taken from period's information
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0028752 closed aferraz Localization Pack: Spain 303 Year information should be considered from period's information instead of name set in Year window 
related to design defect 0028753 closed aferraz Localization Pack: Spain 349 Year information should be considered from period's information instead of name set in Year window 
related to defect 0029065 closed vmromanos Localization Pack: Spain 347 Year information should be considered from period's information instead of name set in Year window 
related to defect 0029067 closed vmromanos Localization Pack: Spain 190 Year information should be considered from period's information instead of name set in Year window 
related to defect 0029068 closed vmromanos Localization Pack: Spain 390 Year information should be considered from period's information instead of name set in Year window 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-10-31 10:31maiteNew Issue
2014-10-31 10:31maiteAssigned To => jonalegriaesarte
2014-10-31 10:31maiteResolution time => 1417388400
2014-10-31 12:06maiteAssigned Tojonalegriaesarte => eduardo_Argal
2014-10-31 12:06maiteIssue Monitored: networkb
2014-10-31 19:04eugeniIssue Monitored: eugeni
2014-10-31 19:08eugeniNote Added: 0071318
2014-12-15 13:33SandrahuguetNote Added: 0072509
2015-01-13 18:01fsoto82Statusnew => scheduled
2015-01-13 18:01fsoto82Assigned Toeduardo_Argal => fsoto82
2015-01-13 18:01fsoto82fix_in_branch => pi
2015-02-13 11:08psanjuanRelationship addedrelated to 0028752
2015-02-18 11:30SandrahuguetRelationship addedrelated to 0028753
2015-02-25 16:37vmromanosIssue cloned0029065
2015-02-25 16:37vmromanosRelationship addedrelated to 0029065
2015-02-25 17:58vmromanosRelationship addedrelated to 0029067
2015-02-25 18:16vmromanosRelationship addedblocks 0029068
2015-02-25 18:16vmromanosRelationship deletedblocks 0029068
2015-02-25 18:17vmromanosRelationship addedrelated to 0029068
2015-02-26 14:01vmromanosNote Added: 0074969
2015-02-26 14:01vmromanosStatusscheduled => resolved
2015-02-26 14:01vmromanosResolutionopen => fixed
2015-02-26 14:07psanjuanNote Added: 0074971
2015-02-26 14:07psanjuanStatusresolved => closed
2015-02-26 14:07psanjuanfix_in_branchpi =>

Notes
(0071318)
eugeni   
2014-10-31 19:08   
Notice that this is specially relevant when you use a calendar for accounting purposes that does not map with the natural year, for instance, from July to June as many football clubs or from September to August as Education institutions.
(0072509)
Sandrahuguet   
2014-12-15 13:33   
This issue should be fixed for the following reports:

347,303, 390, 190, 349
(0074969)
vmromanos   
2015-02-26 14:01   
All modules affected are fixed
(0074971)
psanjuan   
2015-02-26 14:07   
Issue closed as all issues related to this one are already closed.