...
For shared filters, the app detects whether one of the columns is date identifies if a column contains dates or date-time values. If yesit does, it provides a filtering option for those fields is available with date-selecting a date range or date-time - range.
Moreover, it is now possible to filter by project, fix versions, or by component (for company-managed projects).
...
While using the External Share Lite version, if the share configurations were changed during the share configuration process, it caused an infinite loading and an error message. After solving this, users are now able to create shares and the autosave does not disrupt this process.
___
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
- when I create a filter, I need to choose the project, so why filter by project?
- what is “fix version”?
- I’ve read what are components, but still not sure - why there are allowed only for company-managed projects (and what does it mean)?
we don’t use component or fix versions?…
I’ve merged both JQL-related improvements into one note
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Fixed issue layouts deletion
| Status | ||||
|---|---|---|---|---|
|
After every application update, custom issue layouts for external shares were restored to default values. Settings are now being maintained.