The database query that filters the orders by several fields is used only when
the subelements checkbox is not clicked. Otherwise the old query is used and the
old behavior is kept for the filtering.
However, if the checkbox is not clicked, the new query is used to get the
initial list and to do the successive filtering too.
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
This was causing that the messages to show or not depending on the success
operation were not working properly.
Moreover, it has been updated the messages to give more information to the user.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
If JIRA is not activated the part to do the synchronization with the server in
the project edition shouldn't be visible.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
This allows user to change to WBS tab and see the imported tasks just after
import the issues from JIRA.
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
This patch allows the user to store a URL or a comma-separated list of words to
specify the possible labels for the JIRA connector.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
JIRA issues code is not editable in the WBS and it shouldn't be editable in the
task edition pop-up either.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
When you enter in the edition of a task in the WBS, if the task is a JIRA issue,
when you come back to the WBS LibrePlan was trying to update the code column,
however this column doesn't exist for JIRA issues as we're using a link.
Fixed that to avoid an exception in this situation.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
If the comment length is lower than the max length of the DescriptionField, then
it's not needed to truncate it.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
In order to avoid exceptions accessing to an URL, the calls to WebClient.create
have been enclosed into try/catch statements, logging the exception and showing
an appropriate message to the user.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
This reverts commit f3bec8193f.
Because of it was causing some issues:
* The WBS was not loaded properly after synchronization
* WorkReports cannot be saved as the order elements where not saved yet
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
As we know that the predefined WorkReportType will only have 1 DescriptionValue,
we can take advantage of this to simplify the code.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
The code was being generated in 2 parts, first for the query and then to be set.
As in other cases if the WorkReportLine is found by code, we don't need to set
it again. So the part related to manage the code has been moved close to the
query and only set for newly created objects.
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
User should be able to do not save if he is not happy with the result of the
JIRA importation.
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
Some tests only passes if you have a JIRA server installed, as it's not
something mandatory to run LibrePlan, these tests are ignored by default.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
In order to simply code of JiraSyncInfo it has been used the method
Collections.unmodifiableList. Moreover, the type of syncFailedReasons has been
changed to List to make it easier.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
* Extracted paths for JIRA REST API to constants.
* Code simplification:
* Use StringUtils.split
* Use Collections.singletonList
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
* Extract save part to a separated method as syncJiraTimesheetWithJiraIssues
doesn't deal with workReportModel and it could cause misunderstandings.
* Move some parts just needed for newly created objects inside the ifs.
* Use properly EffortDuration to create a new one from seconds.
* Avoid find in another transaction as transaction is already opened.
FEA: ItEr77S16JiraAndTimConnectorContributionIntegration
