Since the "foreign key" constraint with onDelete parameter introduced into liquibase is handling
at database level the integrity, the external operations to clean the setting values are not longer
needed.
FEA: ItEr77S15FilteringEnhancements
In this way it's possible to get all the projects for wich some part of their lenght is
comprehended between the defined start and end dates, with the previous strategy only the
projects which were completely included in the interval were being listed.
FEA: ItEr77S15FilteringEnhancements
If the list of unscheduled projects is empty, the restriction shouldn't be added
or it'll cause a syntax error due to an empty list "o.id IN ()".
FEA: ItEr77S15FilteringEnhancements
When you import a project from the web service, the task elements are not
created yet, so we need to return these projects in the query otherwise they
will be not visible at all for the users.
FEA: ItEr77S15FilteringEnhancements
The new query receives several params from the filters (dates, labels, criteria,
customer and state) and returns the filtered orders.
For the moment it's only used to get the initial list of orders for the projects
list window.
FEA: ItEr77S15FilteringEnhancements
As this field could be used to store a list of labels, it's better that it's
longer than 255 chars.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
Due to previous commit, this field could save a URL or a list of labels, so the
name has been changed to avoid misunderstandings.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
* The predefined type will have a line description value to store comments in
each line.
* As for the case of personal timesheets the new type will be hidden for the
users in the list of timesheets templates.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
* A new method isJiraIssue has been added to OrderElement checking if the code
uses the JIRA prefix or not.
* The method Util.bind has been removed as it was specific of this link and only
used in one place.
* To calculate issue code for the link it has been used StringUtils.removeStart.
TODO: Pending to disable hours in WBS if the task is a JIRA issue.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
* Renamed PersonalTimesheetsTypeOfWorkHoursBootstrap to
ConfigurationTypeOfWorkHoursBootstrapa in order to set up TypeOfWorkHours for
both personal timesheets and Jira connector.
* Modified ConfigurationBootstrap to ensure that the JiraConfiguration is
created properly.
* Removed unneeded code in ConfigurationModel.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
* The new field is added in JiraConfiguration similar to field
Configuration.personalTimesheetsTypeOfWorkHours.
* Added required bits for Hibernate mapping and Liquibase database changes.
* Modified Jira connector configuration UI to include the new field.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
As the same prefix is used in several files it has been defined as a constant in
JiraConfiguration.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
Missing protected constructor in order to avoid wrong usage of the class (maybe
someone could try to do "new JiraConfiguration()" instead of
JiraConfiguration.create()).
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
When order elements of an existing order are synchronized for an specified label, the specified
label will be stored in order_table. This is to prevent that different labels being imported for
the specified order
The issue was introduced in commit 05132fd5a7.
Where it was defined an algorithm:
2.4) FSD is not null and FED is not null:
2.4.1) APED is null: Check if APSD is between FSD and FED
This was wrong, it should be:
2.4) FSD is not null and FED is not null:
2.4.1) APED is null: Check if APSD is lower or equals than FSD or APSD is
lower or equals than FED
FEA: ItEr77S04BugFixing
Now the dates filtering the resource load window are checked against the
resources activation periods. Using the following algorithm:
1) If the resource has not activation periods then it should always appear
2) The filter can have null for start and end dates and the activation periods
can have null for end date. So we should define what to do in each case:
Let's define some acronyms:
* Filter Start Date: FSD
* Filter End Date: FED
* Activation Period Start Date: APSD (cannot be null)
* Activation Period End Date: APED
2.1) FSD is null and FED are null: The resource should appear regardless its
activation periods
2.2) FSD is null:
2.2.1) APED is null: Check if APSD is lower or equals than FED
2.2.2) APED is not null: Check if APSD is lower or equals than FED or APED
is lower or equals than FED
2.3) FED is null:
2.3.1) APED is null: The resource should appear
2.3.2) APED is not null: Check if APSD is later or equals than FSD or APED
is later or equals than FSD
2.4) FSD is not null and FED is not null:
2.4.1) APED is null: Check if APSD is between FSD and FED
2.4.2) APED is not null: Check if activation period overlaps filter period
at any point
FEA: ItEr77S04BugFixing
