Since the scenario was created in the same transaction (due to using
@Before annotation) was not visible in givenOrderFromPrepareForCreate.
Now use a @BeforeTransaction instead so it's visible before.
Otherwise it creates a new Spring context instead of keeping using the
previous one.
This doesn't seem specially dangerous, but in some circumstances can
lead to idle transactions with associated locks that hang up the
execution of the tests. This happened with PostgreSQL version 9.1 in
WorkReportServiceTest.importValidDescriptionValuesToWorkReport().
This reverts commit 9a8d7deffe7bb5034448f698ab3dff4014b1bdb1.
The original fix on the patch "Bug #1546: Force recalculation of critical path progresses on
saving project" is having a side-effect on the behaviour of the dependencies, that don't push
tasks and are show violated.
As the regression effect is more severe than the original bug, we revert the patch while finding
another solution for the original issue.
The links on the breadcrumbs line were problematic as they
were pointing to the first subelement of the current section of the
menu, which could be an element unauthorized for the user.
As these shortcats are not useful enough and redundant with the main menu,
which can be used directly as is showing only the entries to the specific
user has access to, the links in this components are removed.
FEA: ItEr77S04BugFixing
On the chinese translation of the dashboard a formatting exception was being raised
due to the way the i18n methods were being called.
FEA: ItEr77S04BugFixing
An additional check is introduced to limit access to planning perspective of a project
to which the user doesn't have permissions. The MessageBox modal operation might be moved
out to show nicely the error information.
FEA: ItEr77S04BugFixing
Two margins have been added:
* A margin before the task start date.
* A margin after the task end date.
The time used in these two margins has been the same and is equal to 30 days.
FEA: ItEr77S10ResourceAllocationLoadInformation
It has been improved the performance so that the search of the resources and their
load ratios calculation is done from this moment on when the advanced search tab is made visible. This is
the moment when the task start date and task end date are available (not
sooner).
FEA: ItEr77S10ResourceAllocationLoadInformation
This is managed now at JiraSynchronizationController.showOrHideJiraEditWindow()
and TimSynchronizationController.showOrHideTimEditWindow().
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
- In OrderSyncInfoDAO the method name findByKeyAndConnectorId is changed to findByKeyOrderAndConnectorId and
a parameter Order is added. The files that uses this method are modified accordingly
- In JiraSynchronizationController refresh added. If OrderSyncInfo is saved the jira sync info screen will be
updated to show the change
- OrderCRUDController refactored
- Save or update for OrderSyncInfo instead of creating new instance for each sync
- Name change for TimImpExpInfo to SynchronizationInfo
- JiraSyncInfo is removed instead SynchronizationInfo is used
- All files which are affected by name changes are modified
- Translations added where applicable
- clean up unused variables etc
The problem was that when you add a child to a newly created empty task, it
become the task in a container, and then mark the container as selected to ease
the insertion of new children.
In order to mark the container as selected the element needs to be renderer
before we try to select it, otherwise we have been getting a NPE.
FEA: ItEr77S04BugFixing
- JIRA is moved to connectors and all files modified that has to do with this change.
- JiraConfiguration file is removed
- ImportedLabel attribute is deleted from Order and order.hbm.xml
- Imstead of importedLabel is now used the key from OrderSyncInfo
- and some more changes where applicable
