Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


older | 1 | .... | 3152 | 3153 | (Page 3154) | 3155 | 3156 | .... | 3182 | newer

    0 0

    Reporter Maksim Ryzhikov (maksimrv) Maksim Ryzhikov (maksimrv)
    Created Dec 18, 2018 11:12:15 PM
    Updated Dec 28, 2018 4:21:17 PM
    State In Progress
    Assignee Maxim Erekhinskiy (maxim.erehinskiy)
    Subsystem Issue List
    Type Task
    Priority Normal
    Fix versions Unscheduled

    This issue about performance optimization for rendering issues list , switch between tree and flat view

    Now on the test database, it takes around 2sec to render list with 100 issues


    0 0

    Reporter Beryl Lusen (blinet) Beryl Lusen (blinet)
    Created Dec 12, 2016 8:34:11 PM
    Updated Dec 28, 2018 4:37:36 PM
    Resolved Dec 28, 2018 4:37:36 PM
    State Fixed
    Assignee Evgeny Naumenko (jk)
    Subsystem Upsource Integration
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions 2018.4.next
    Affected versions Unknown
    There appears to be a small error in the way that YouTrack scans for its issue IDs in Upsource review titles; it matches (for example) "[TEST-10]" to both TEST-1 and TEST-10, resulting in the review being associated with both issues.

    What steps will reproduce the problem?

    1. Create a YouTrack project (example. id: "TEST")
    2. Create an Upsource project that uses the YouTrack project as its issue tracker
    3. Open ten issues (will be assigned issue# TEST-1 through TEST-10)
    4. Open a review with its title being something like "[TEST-10] Review of this issue"

    What is the expected result?

    The "VCS changes" tab on YouTrack issue TEST-10 should have a link to the review listed, and no other issues have that link

    What happens instead?

    The link to the review appears as expected in the "VCS changes" tab for TEST-10, but it also appears in changes tab for TEST-1 (where it clearly does not belong).

    Please provide any additional information below.

    YouTrack version: 7.0 Build 29013
    Upsource version: Build 3.5.3550
    Hub version: Build 2.5.359
    All teamware hosted on Linux server running CentOS 7.2

    0 0

    Reporter Alexander Volfman (Alexander.Volfman) Alexander Volfman (Alexander.Volfman)
    Created Jul 5, 2018 10:12:26 AM
    Updated Dec 28, 2018 4:38:06 PM
    Resolved Dec 28, 2018 4:38:06 PM
    State Fixed
    Assignee Evgeny Naumenko (jk)
    Subsystem Upsource Integration
    Type Bug
    Priority Major
    Browser Any Browser
    OS Any OS
    Fix versions 2018.4.next
    Affected versions Unknown
    YouTrack frontend would query Upsource for reviews containing a string equal to issue id (e.g. PR-123). Thus, it can be the case that upsource also returns reviews for issues with ids containing the requested (e.g. PR-1234, or APR-123). So additional filtering needs to be done on YouTrack side.

    0 0

    Reporter Juraj H (jurosh) Juraj H (jurosh)
    Created Jun 24, 2015 9:49:46 PM
    Updated Dec 28, 2018 4:49:14 PM
    State Open
    Assignee Pavel Nikolaev (pasha)
    Subsystem Dashboard & Widgets
    Type Feature
    Priority Normal
    Fix versions Unscheduled
    Would be really nice to see dashboard widget to see latest changes with comments directly visible.
    A widget like that is expected to show all the recent changes within a scope:
    • Changes made by a certain user
    • Changes in scope of a project/saved search
    • Changes for a particular issue
    • Changes for an agile board

    Activity stream (or feed) is highly useful for getting a bird-eye view on what's going on in your project.

    0 0

    Reporter Charles Martin (Fenikkusu) Charles Martin (Fenikkusu)
    Created Dec 27, 2018 1:19:33 AM
    Updated Dec 28, 2018 4:49:14 PM
    State Open
    Assignee Ekaterina Zaikina (Ekaterina_Zaikina)
    Subsystem Dashboard & Widgets
    Type Feature
    Priority Normal
    Fix versions Unscheduled
    I would like to see a report that I can pull from a user/employee management auditing perspective. This report should be able to display all history related to a specific person (or persons) over a given time frame. For example, at the end of the day, I could get a report that tells me that John Doe moved MYPROJECT-123 from open to in progress at 9AM. At 10AM, he moved it back to Open. At 10:05AM, MYPROJECT-456 was moved to in progress. At 10:30, the same ticket was moved from in progress to Awaiting Review and a work log entry was made for 1 Hour (Note The Difference In Time Frame).

    Such a report would allow me to see a couple of things. First, it would allow me to see people 'cheating' on their time frames. Second, I can use such a report to see if they are in between tasks and I just caught them at a bad time. Third, it allows me to get a better idea of their general workflow across the entire day.

    0 0

    Reporter Andrey Skladchikov (Andrey.Skladchikov) Andrey Skladchikov (Andrey.Skladchikov)
    Created Dec 25, 2018 8:52:21 PM
    Updated Dec 28, 2018 4:52:47 PM
    Resolved Dec 28, 2018 4:52:47 PM
    State Fixed
    Assignee Andrey Skladchikov (Andrey.Skladchikov)
    Subsystem User Management
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    0 0

    Reporter Ekaterina Alekseeva (Ekaterina.Alekseeva) Ekaterina Alekseeva (Ekaterina.Alekseeva)
    Created Dec 27, 2018 3:06:26 PM
    Updated Dec 28, 2018 5:13:38 PM
    Resolved Dec 28, 2018 5:13:38 PM
    State Fixed
    Assignee Andrey Skladchikov (Andrey.Skladchikov)
    Subsystem Workflow
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    build 48217

    STR:

    1. Go to Workflows page (/admin/workflows)
    2. Open preview of some rule

    AR:
    Text is too pale

    Compare to same code with dark theme in workflow editor:


    0 0

    Reporter Andrey Skladchikov (Andrey.Skladchikov) Andrey Skladchikov (Andrey.Skladchikov)
    Created Dec 28, 2018 5:15:07 PM
    Updated Dec 28, 2018 5:15:07 PM
    State Open
    Assignee Andrey Skladchikov (Andrey.Skladchikov)
    Subsystem Deprecated Admin
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    It only applies if user turn it off/on


    0 0

    Reporter Ekaterina Alekseeva (Ekaterina.Alekseeva) Ekaterina Alekseeva (Ekaterina.Alekseeva)
    Created Dec 27, 2018 3:13:22 PM
    Updated Dec 28, 2018 5:20:59 PM
    State Open
    Assignee Andrey Skladchikov (Andrey.Skladchikov)
    Subsystem Projects
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    build 48217

    STR: go to Access or Team tab in proejct settings

    AR:
    Selected row is white

    ER:
    Selected row is highlighted with dark blue color (like everywhere else)
    For example, on Fields tab:


    0 0

    Reporter Anastasia Bartasheva (ana.bartasheva) Anastasia Bartasheva (ana.bartasheva)
    Created Nov 27, 2018 4:51:36 PM
    Updated Dec 28, 2018 5:21:50 PM
    State Open
    Assignee Anna Zhdan (Anna.Zhdan)
    Subsystem Search
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions 2018.3.47247
    STR:
    1. Have a board which name includes the 'assignee' word
    2. Go to issue list
    3. Enter sort by: Assignee query

    ER: issues are sorted by assignee
    AR: the sorting doesn't work; the sign under the search bar says that issues are sorted by <board name> (see attached)

    0 0

    Reporter Dmitriy Smirnov (sdv) Dmitriy Smirnov (sdv)
    Created Dec 28, 2018 4:34:57 PM
    Updated Dec 28, 2018 5:26:50 PM
    State Open
    Assignee Alexander Volfman (Alexander.Volfman)
    Subsystem Integrations
    Type Feature
    Priority Normal
    Fix versions Unscheduled

    0 0

    Reporter Ekaterina Alekseeva (Ekaterina.Alekseeva) Ekaterina Alekseeva (Ekaterina.Alekseeva)
    Created Dec 28, 2018 5:28:07 PM
    Updated Dec 28, 2018 5:31:16 PM
    State Open
    Assignee Alexander Anisimov (xi-eye)
    Subsystem Single Issue View
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    build 48437

    STR:

    1. Log in as user without Read Group permission (e.g. with only Developer role)
    2. Go to some issue and start editing comment
    3. Try to change 'Visible to' setting

    AR:
    There's no 'Visible to' control

    The same user can still set visibility to new comments or edit visibility for issues and attachments.


    0 0

    Reporter Ekaterina Alekseeva (Ekaterina.Alekseeva) Ekaterina Alekseeva (Ekaterina.Alekseeva)
    Created Dec 27, 2018 3:18:37 PM
    Updated Dec 28, 2018 5:35:46 PM
    State To be discussed
    Assignee Andrey Skladchikov (Andrey.Skladchikov)
    Subsystem No Subsystem
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    build 48217

    STR:

    1. Go to /admin/notificationTemplates

    2. Open preview for some template
      AR:

    3. Open template editor
      AR:


    0 0

    Reporter Ekaterina Alekseeva (Ekaterina.Alekseeva) Ekaterina Alekseeva (Ekaterina.Alekseeva)
    Created Dec 27, 2018 3:23:17 PM
    Updated Dec 28, 2018 5:35:54 PM
    Resolved Dec 28, 2018 5:35:54 PM
    State Fixed
    Assignee Andrey Skladchikov (Andrey.Skladchikov)
    Subsystem Agile Board
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    build 48217

    STR:

    1. Open some agile board
    2. Drag some card from backlog to board (or move it within backlog)

    AR:
    Dragged card preview is white


    0 0
  • 12/28/18--06:36: JT-50313: FSI Mobile review
  • Reporter Dmitry Gizatov (mitya) Dmitry Gizatov (mitya)
    Created Nov 15, 2018 2:00:57 PM
    Updated Dec 28, 2018 5:36:08 PM
    Resolved Dec 28, 2018 5:36:01 PM
    State Fixed
    Assignee Alexander Anisimov (xi-eye)
    Subsystem Single Issue View
    Type Task
    Priority Normal
    Fix versions 2018.4.48293, 2018.3.next


    0 0

    Reporter Pavlo Zhukov (grodas.p35) Pavlo Zhukov (grodas.p35)
    Created Jul 4, 2018 10:20:41 AM
    Updated Dec 28, 2018 5:44:03 PM
    State Open
    Assignee Andrey Skladchikov (Andrey.Skladchikov)
    Subsystem No Subsystem
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions 2018.4.next
    Affected versions Unknown
    How to reproduce
    1. I've opened issue from a blog article
    2. Noticed new design and switch to the dark theme
    3. Noticed agreement request and press on it


    Recorded example

    0 0

    Reporter Joel Feiner (SHJoelFeiner) Joel Feiner (SHJoelFeiner)
    Created Nov 5, 2015 8:33:29 PM
    Updated Dec 28, 2018 5:55:40 PM
    Resolved Dec 3, 2018 3:04:13 PM
    State Verified
    Assignee Leonid Stryuk (Leonid.Stryuk)
    Subsystem Integrations
    Type Usability Problem
    Priority Major
    Browser Any Browser
    OS Any OS
    Fix versions 2018.4.48293
    Affected versions 6.5
    In the Monitor Branches section of the GitLab Integration configuration for a project, the in-line documentation says to use specs of the form '+|-:<branch name>'. This implies that you can use "+:master". But in fact, you have to say "+:refs/heads/master". Either the documentation should be updated, or the integration should allow "+:master".

    0 0

    Reporter Marko Bozac (mbozac) Marko Bozac (mbozac)
    Created Dec 28, 2018 6:58:29 PM
    Updated Dec 28, 2018 6:58:29 PM
    State Submitted
    Assignee Unassigned
    Subsystem No Subsystem
    Type Feature
    Priority Normal
    Fix versions Unscheduled

    What steps will reproduce the problem?

    1. Create a board (or pick existing one)
    2. Add feature/bug on a board as a swimlane
    3. Add tag on feature (issue shown as swimlane on the board) tag is not shown

    What is the expected result?
    I would expect to see a tag of that feature (inline, next to issue name or ID)

    What happens instead?
    Tag is not shown.

    Please provide any additional information below.
    Attach a code sample as text, a screenshot or screencast if possible

    We use features and bugs as swimlanes and tasks bellow it as tasks to be done as part of bug of feature fix. When something needs to be patched (deployed to prod) before end of the sprint, we use tag to mark bug as something for patch. It would be much helpful if tag would be visible on a swimlane instead only on details of issue which we need to open every time and check if it has a tag. For example:


    0 0

    Reporter Alexander Buturlinov (alexander.buturlinov) Alexander Buturlinov (alexander.buturlinov)
    Created Dec 18, 2018 7:12:35 PM
    Updated Dec 28, 2018 8:10:05 PM
    State Wait for Reply
    Assignee Alexander Volfman (Alexander.Volfman)
    Subsystem GitHub Integration
    Type Bug
    Priority Normal
    Browser Any Browser
    OS Any OS
    Fix versions Unscheduled
    Affected versions Unknown

    STR:

    1. Setup GitHub integration for a project and a repository
    2. Make a commit and mention some issue
    3. Wait a little while commit to be processed
    4. Go to GitHub -> your repo -> WebHooks, find Recent Deliveries section and check the latest commit status.

    GitHub reports that the delivery failed with code 403. But at the same time the commit is normally processed in YT.

    18/12/18 18:06:15,869 INFO  [@qtp758705033-20] [VcsHooksReceiverResource      ] [internal@xxx.xxx.xxx.xxx] GithubServer.hookCalled
    18/12/18 18:06:15,874 INFO  [@qtp758705033-20] [ChangesProcessorImpl          ] [internal@xxx.xxx.xxx.xxx] [GitHub Integration SP<-boot85/test-x (branch spec: +:*)]: Process configuration
    18/12/18 18:06:15,877 INFO  [@qtp758705033-20] [ChangesProcessorImpl          ] [internal@xxx.xxx.xxx.xxx] [GitHub Integration SP<-boot85/test-x (branch spec: +:*)]: Processing changes 72040f8d29b3d86d76b6b61c9c7b6ccff4443012
    18/12/18 18:06:15,930 INFO  [@qtp758705033-20] [ChangesProcessorImpl          ] [root@xxx.xxx.xxx.xxx] [GitHub Integration SP<-boot85/test-x (branch spec: +:*)]: Processing changes 
    


    0 0

    Reporter Anastasia Bartasheva (ana.bartasheva) Anastasia Bartasheva (ana.bartasheva)
    Created Dec 28, 2018 8:29:53 PM
    Updated Dec 28, 2018 8:30:01 PM
    State Open
    Assignee Anna Zhdan (Anna.Zhdan)
    Subsystem Search
    Type Feature
    Priority Normal
    Fix versions Unscheduled

older | 1 | .... | 3152 | 3153 | (Page 3154) | 3155 | 3156 | .... | 3182 | newer