In order to avoid to have the same user in the session twice, the validation
query of User entity has been done in a different transaction.
The issue happens with resources too, so the same solution has been used in
both cases.
FEA: ItEr77S04BugFixing
* Renamed .zul file and page to "Job Scheduling".
* Include ROLE_JOB_SCHEDULING in default profile SYSTEMS_ADMINISTRATOR.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
This allows to add a task over a leaf in a filtered WBS, and being able to keep
seeing the 3 elements: the new container (with the name of the previous leaf),
the previous leaf without name and the new task added.
It's easier to understand with an example. Imagine you have the following WBS:
* Task 1
* Task 2
And you filter by task name using "2", then you'll have:
* Task 2
Then you select "Task 2" and add a new task called "Subtask A".
Without this patch you'll only see:
* Task 2 (the new container using the name of the old leaf)
|- Subtask A (the new task)
However, it's better you see the following
* Task 2 (the new container using the name of the old leaf)
|- (empty task) (the old leaf that you should rename)
|- Subtask A (the new task)
FEA: ItEr77S15FilteringEnhancements
DTO classes are renamed to class-name with suffix DTO according to Libreplan naming convention
Modified all classes which are affected by the renamed classes
Comments and author information added where applicable
Test cases modified
Three tables added:
order_sync_info: holds the order synchronization information
app_properties: holds app configuration properties
job_scheduler_configuratiion: holds job to be scheduled
Both app_properties and job_scheduler_configurations are filled with default values
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
