| Reporter |
Anna Zhdan (Anna.Zhdan)
|
|---|---|
| Created | Nov 30, 2018 3:21:51 PM |
| Updated | Nov 30, 2018 3:21:51 PM |
| State | Open |
| Assignee | Unassigned |
| Subsystem | No Subsystem |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
JT-50613: Write rest tests in YT
↧
↧
JT-50440: не меняется рабочий процесс
| Reporter |
Ditriy Kalinyuk (kalinjuk)
|
|---|---|
| Created | Nov 22, 2018 4:43:14 PM |
| Updated | Nov 30, 2018 3:34:35 PM |
| State | Wait for Reply |
| Assignee | Oleg Larshin (Oleg.Larshin) |
| Subsystem | No Subsystem |
| Type | Support Request |
| Priority | Normal |
| Browser | Any Browser |
| OS | Any OS |
| Fix versions | Unscheduled |
| Affected versions | Unknown |
Есть проект и есть рабочий процесс привязанный к нему, в нем прописаны 4 значения для перехода из поля Состояние.
А в задачах есть только переход в 3 значения, полный скрипт во вложении
скрины во вложении
What is the expected result?
What happens instead?
Please provide any additional information below.
Attach a code sample as text, a screenshot or screencast if possible
↧
JT-50213: Email notifications for assignee change stopped working
| Reporter |
Tomas Grunwald (tgrunwald)
|
|---|---|
| Created | Nov 8, 2018 12:06:42 PM |
| Updated | Nov 30, 2018 3:39:31 PM |
| State | Open |
| Assignee | Pavel Nikolaev (pasha) |
| Subsystem | Notifications |
| Type | Bug |
| Priority | Major |
| Browser | Any Browser |
| OS | Any OS |
| Fix versions | Unscheduled |
| Affected versions | 2018.2.42881 |
On our Youtrack server the mail notifications about assignee change stopped to be delivered.
When I try to look at notification templates->Issue Change->Issue digest, always the message about overloaded server pops up
and in errors log appear following error: 08/11/18 10:01:29,334 ERROR [@946525153-66259] [ErrorExceptionMapper ] [tomas.grunwald@192.168.1.96] Caught ex
ception during request processing at POST /api/admin/notificationSupplement/preview requested by Mozilla/5.0 (Windows N
T 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
java.lang.ClassCastException: null
Any hints how to fix?
Attached our latest logs.
Thank You
↧
JT-50042: Unable to upload workflows since 2018.3
| Reporter |
Andrea Sciamanna (sciamannikoo)
|
|---|---|
| Created | Oct 30, 2018 1:55:34 PM |
| Updated | Nov 30, 2018 3:43:28 PM |
| State | In Progress |
| Assignee | Anna Zhdan (Anna.Zhdan) |
| Subsystem | Workflow |
| Type | Bug |
| Priority | Normal |
| Browser | Any Browser |
| OS | Any OS |
| Fix versions | Unscheduled |
| Affected versions | Unknown |
Every time I try to upload a workflow, even an unchanged one, I get this:
npm run upload-prod -- otgs-notifications
> youtrack-workflows@1.0.0 upload-prod /{undisclosed path}
> cross-env youtrack-workflow upload --host=$npm_config_host_prod --token=$npm_config_token_prod "otgs-notifications"
Error: [403] HTTP 403 Forbidden
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! youtrack-workflows@1.0.0 upload-prod: `cross-env youtrack-workflow upload --host=$npm_config_host_prod --token=$npm_config_token_prod "otgs-notifications"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the youtrack-workflows@1.0.0 upload-prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /{undisclosed path}/.npm/_logs/2018-10-30T10_40_54_719Z-debug.log
I've checked the log file and I can't see anything more relevant that what's above:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/10.11.0/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'upload-prod',
1 verbose cli '--',
1 verbose cli 'otgs-notifications' ]
2 info using npm@6.4.1
3 info using node@v10.11.0
4 verbose run-script [ 'preupload-prod', 'upload-prod', 'postupload-prod' ]
5 info lifecycle youtrack-workflows@1.0.0~preupload-prod: youtrack-workflows@1.0.0
6 info lifecycle youtrack-workflows@1.0.0~upload-prod: youtrack-workflows@1.0.0
7 verbose lifecycle youtrack-workflows@1.0.0~upload-prod: unsafe-perm in lifecycle true
8 verbose lifecycle youtrack-workflows@1.0.0~upload-prod: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/{undisclosed path}/www/wpml-development/app/public/otgs-shared/youtrack-workflows/node_modules/.bin:/usr/local/sbin:/{undisclosed path}/.composer/vendor/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle youtrack-workflows@1.0.0~upload-prod: CWD: /{undisclosed path}/www/wpml-development/app/public/otgs-shared/youtrack-workflows
10 silly lifecycle youtrack-workflows@1.0.0~upload-prod: Args: [ '-c',
10 silly lifecycle 'cross-env youtrack-workflow upload --host=$npm_config_host_prod --token=$npm_config_token_prod "otgs-notifications"' ]
11 silly lifecycle youtrack-workflows@1.0.0~upload-prod: Returned: code: 1 signal: null
12 info lifecycle youtrack-workflows@1.0.0~upload-prod: Failed to exec upload-prod script
13 verbose stack Error: youtrack-workflows@1.0.0 upload-prod: `cross-env youtrack-workflow upload --host=$npm_config_host_prod --token=$npm_config_token_prod "otgs-notifications"`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:182:13)
13 verbose stack at maybeClose (internal/child_process.js:962:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid youtrack-workflows@1.0.0
15 verbose cwd /{undisclosed path}/www/wpml-development/app/public/otgs-shared/youtrack-workflows
16 verbose Darwin 18.0.0
17 verbose argv "/usr/local/Cellar/node/10.11.0/bin/node" "/usr/local/bin/npm" "run" "upload-prod" "--" "otgs-notifications"
18 verbose node v10.11.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error youtrack-workflows@1.0.0 upload-prod: `cross-env youtrack-workflow upload --host=$npm_config_host_prod --token=$npm_config_token_prod "otgs-notifications"`
22 error Exit status 1
23 error Failed at the youtrack-workflows@1.0.0 upload-prod script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Downloading workflows work just fine. The problem is with the uploading.
I've also checked the token and even generated a new one with no changes.
↧
JT-50501: Test manually
| Reporter |
Anna Zhdan (Anna.Zhdan)
|
|---|---|
| Created | Nov 26, 2018 4:56:25 PM |
| Updated | Nov 30, 2018 3:49:47 PM |
| State | In Progress |
| Assignee | Alexander Buturlinov (alexander.buturlinov) |
| Subsystem | No Subsystem |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
↧
JT-50614: Display Agile Board associated with ticket at all time
| Reporter |
Kruno Golubić (kruno.g)
|
|---|---|
| Created | Nov 30, 2018 4:01:40 PM |
| Updated | Nov 30, 2018 4:01:40 PM |
| State | Submitted |
| Assignee | Unassigned |
| Subsystem | Issue Creation |
| Type | Feature |
| Priority | Normal |
| Fix versions | Unscheduled |
It would be great if a name of the agile board(s) Agile Board associated with the ticket would be displayed all the time without a need to click on Boards to show it.
↧
JT-50538: table: data part (columns for dates) scrollable
| Reporter |
Alexey Volkov (Alexey.Volkov)
|
|---|---|
| Created | Nov 27, 2018 4:23:07 PM |
| Updated | Nov 30, 2018 4:26:21 PM |
| State | In Progress |
| Assignee | Alexey Volkov (Alexey.Volkov) |
| Subsystem | Reports |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
JT-50615: Clean up wording on Global Settings page
| Reporter |
Scott Adams (Scott.Adams)
|
|---|---|
| Created | Nov 8, 2018 1:55:36 PM |
| Updated | Nov 30, 2018 4:26:47 PM |
| State | In Progress |
| Assignee | Scott Adams (Scott.Adams) |
| Subsystem | No Subsystem |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
We need to update wording to conform to guidelines for UI text:
- Use sentence case for field labels.
- Provide placeholder text when values are expected to conform to a specific pattern.
- For explanatory text, don't use a period after a single sentence. If two or more sentences run together, use a period for each sentence.
- Start link text with a verb that describes what happens when the user clicks the link.
- Don't add periods at the end of link text.
↧
JT-50535: Save new issue's position on the server after drag & drop
| Reporter |
Maksim Ryzhikov (maksimrv)
|
|---|---|
| Created | Nov 27, 2018 3:23:25 PM |
| Updated | Nov 30, 2018 4:33:36 PM |
| State | Open |
| Assignee | Unassigned |
| Subsystem | Issue List |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
↧
JT-50569: Implement `api/sortedIssues` endpoint
| Reporter |
Alexander Anisimov (xi-eye)
|
|---|---|
| Created | Nov 28, 2018 6:26:50 PM |
| Updated | Nov 30, 2018 4:35:14 PM |
| Resolved | Nov 30, 2018 4:35:14 PM |
| State | Fixed |
| Assignee | Leonid Stryuk (Leonid.Stryuk) |
| Subsystem | No Subsystem |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
api/sortedIssues?query='XX'&folderId=contextFolderId&flatten
should returns
{
numberOfOrdered: int,
count: int,
tree: [ {id, parentId, matches} ]
}
↧
JT-50013: Subtree folding
| Reporter |
Anna Zhdan (Anna.Zhdan)
|
|---|---|
| Created | Oct 29, 2018 5:40:54 PM |
| Updated | Nov 30, 2018 4:45:00 PM |
| Resolved | Nov 30, 2018 4:45:00 PM |
| State | Fixed |
| Assignee | Alexander Anisimov (xi-eye) |
| Subsystem | Issue List |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
JT-50617: Agile: replace inlined HEX colors with Ring UI CSS Variables
| Reporter |
Andrey Skladchikov (Andrey.Skladchikov)
|
|---|---|
| Created | Nov 30, 2018 4:51:16 PM |
| Updated | Nov 30, 2018 4:51:16 PM |
| State | Open |
| Assignee | Unassigned |
| Subsystem | Agile Board |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
JT-50618: FSI: replace inlined HEX colors with Ring UI CSS Variables
| Reporter |
Andrey Skladchikov (Andrey.Skladchikov)
|
|---|---|
| Created | Nov 30, 2018 4:51:44 PM |
| Updated | Nov 30, 2018 4:51:44 PM |
| State | Open |
| Assignee | Unassigned |
| Subsystem | Single Issue View |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
↧
JT-50620: Issue List: replace inlined HEX colors with Ring UI CSS Variables
| Reporter |
Andrey Skladchikov (Andrey.Skladchikov)
|
|---|---|
| Created | Nov 30, 2018 4:52:30 PM |
| Updated | Nov 30, 2018 4:52:30 PM |
| State | Open |
| Assignee | Unassigned |
| Subsystem | Issue List |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
JT-50616: Issue does not dissapear after delete
| Reporter |
Maksim Ryzhikov (maksimrv)
|
|---|---|
| Created | Nov 30, 2018 4:44:12 PM |
| Updated | Nov 30, 2018 5:00:01 PM |
| Resolved | Nov 30, 2018 5:00:00 PM |
| State | Fixed |
| Assignee | Maksim Ryzhikov (maksimrv) |
| Subsystem | Issue List |
| Type | Bug |
| Priority | Normal |
| Browser | Any Browser |
| OS | Any OS |
| Fix versions | Unscheduled |
| Affected versions | Unknown |
↧
JT-50619: Navigation does not work
| Reporter |
Maksim Ryzhikov (maksimrv)
|
|---|---|
| Created | Nov 30, 2018 4:52:05 PM |
| Updated | Nov 30, 2018 5:00:01 PM |
| Resolved | Nov 30, 2018 5:00:01 PM |
| State | Fixed |
| Assignee | Maksim Ryzhikov (maksimrv) |
| Subsystem | Issue List |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
Cannot read property 'getIssues' of undefined
↧
JT-50621: Show description for L (Detailed) view
| Reporter |
Alexander Anisimov (xi-eye)
|
|---|---|
| Created | Nov 30, 2018 5:09:42 PM |
| Updated | Nov 30, 2018 5:09:42 PM |
| State | In Progress |
| Assignee | Alexander Anisimov (xi-eye) |
| Subsystem | Issue List |
| Type | Task |
| Priority | Normal |
| Fix versions | Unscheduled |
↧
↧
JT-38756: CORS whitelist doesn't provide information on format
| Reporter |
Hadi Hariri (hadihariri)
|
|---|---|
| Created | Nov 18, 2016 3:27:07 PM |
| Updated | Nov 30, 2018 5:30:22 PM |
| State | In Progress |
| Assignee | Evgeny Naumenko (jk) |
| Subsystem | No Subsystem |
| Type | Task |
| Priority | Normal |
| Fix versions | 2018.3.next |
The screen below which is required not only for REST API but also Dashboard (obviously consequence of it using REST API)
![]()
doesn't give any information about the format requires to enter CORS origins. Pressing on the Details provides no information since it focuses on the API. Given not all developers are aware of CORS and this applies to usage of Dashboard, it would be good to provide a small sample similar to what TeamCity does on input boxes.
doesn't give any information about the format requires to enter CORS origins. Pressing on the Details provides no information since it focuses on the API. Given not all developers are aware of CORS and this applies to usage of Dashboard, it would be good to provide a small sample similar to what TeamCity does on input boxes.
↧
JT-31023: GitHub integration selects strange repository by default
| Reporter |
Oleg Stepanov (oleg.stepanov)
|
|---|---|
| Created | Jul 27, 2015 7:36:17 PM |
| Updated | Nov 30, 2018 5:35:27 PM |
| Resolved | Nov 30, 2018 5:35:27 PM |
| State | Obsolete |
| Assignee | Alexander Volfman (Alexander.Volfman) |
| Subsystem | GitHub Integration |
| Type | Usability Problem |
| Priority | Normal |
| Browser | Any Browser |
| OS | Any OS |
| Fix versions | Unscheduled |
| Affected versions | Unknown |
It should select the first repository owned by the user
↧
JT-37353: All issues' linked commits under VCS tab disappeared after we re-setup the GitHub integration (to same repo)
| Reporter |
Lars Magne Monsen (lmm.1)
|
|---|---|
| Created | Sep 2, 2016 10:40:01 AM |
| Updated | Nov 30, 2018 5:40:15 PM |
| Resolved | Nov 30, 2018 5:40:10 PM |
| State | Fixed |
| Assignee | Alexander Volfman (Alexander.Volfman) |
| Subsystem | GitHub Integration |
| Type | Support Request |
| Priority | Normal |
| Browser | Any Browser |
| OS | Any OS |
| Fix versions | Unscheduled |
| Affected versions | 6.5 |
For me this is a bug, but you might also consider it a usability problem.
What steps will reproduce the problem?
1. Set up an integration from a YouTrack project to a GitHub repository
2. Add and push commits to the given repo, with YouTrack references/commands
3. Make sure that the commits are listed under the respective issue's VCS tab
4. In YouTrack, add other commit(s) manually under VCS tab (by entering the SHA)
5. Delete the integration in YouTrack and set it up again (from the same YouTrack project to the same GitHub repo)
What is the expected result?
What happens instead?
If the feature suggested in JT-30959 was possible, we would now only have lost the links to manually added commits.
This is quite a loss for us. Would this be stored as hidden data or do you have some kind of backup that could help us get this back?
What steps will reproduce the problem?
1. Set up an integration from a YouTrack project to a GitHub repository
2. Add and push commits to the given repo, with YouTrack references/commands
3. Make sure that the commits are listed under the respective issue's VCS tab
4. In YouTrack, add other commit(s) manually under VCS tab (by entering the SHA)
5. Delete the integration in YouTrack and set it up again (from the same YouTrack project to the same GitHub repo)
- We had to do this with a different GitHub user and token, but after testing I see that it's the actual deletion of the existing integration that apparently also deletes all linked commits for this integration, as it doesn't matter if the integration is re-setup with the exact same user and token. Commits still disappear on integration delete.
What is the expected result?
- The YouTrack issues' linked commits under VCS tab should still be available. Even if the integration was deleted and not re-setup, the info should still have been there, possibly without (working) links.
- Alternatively, when selecting to delete the integration, warn that this is going to happen (e.g. "678 linked commits will be deleted from related issues, confirm delete")
- Alternatively, ask if you want to keep the linked commits (possibly with dead links until the integration is set up again).
What happens instead?
- All YouTrack issues' linked commits (for this integration) are removed from the VCS tab without further notice (in our case hundreds)
If the feature suggested in JT-30959 was possible, we would now only have lost the links to manually added commits.
This is quite a loss for us. Would this be stored as hidden data or do you have some kind of backup that could help us get this back?
↧
More Pages to Explore .....
