Losing characters while typing

As more people on my team are starting to use YouTrack I've been getting a lot of feedback.  A couple things recently came up.  I'm wondering if this is a known issue and if there is anything we can do to mitigate it.

1. (Question) When typing into the summary text box we often see characters dropped.  At first I had attributed this to me mistyping something but it happens consistently and it looks like it's related to the "similar issues" search happening in the background.  Hiding "similar searches" doesn't appear to actually turn off the search, just the UI, so it still happens.  It's usually just a few characters in the middle of a word.  Is there any way to address this?  E.g. can I turn off the feature altogether? (I think it's a great idea, but not at this cost).

2. (Feedback) There has been some confusion due to the "Create Issue" button's behavior.  Clicking it initially brings up the new issue dialog, but on that screen there are now two buttons labeled "Create Issue": The blue one on the bottom that should be clicked (commit) and the orange one at the top which effectively cancels the new issue.  It would be much clearer if the orange button didn't retain the same text and also didn't have that behavior.

Thanks,
8 comments
Comment actions Permalink
Hello Joe,

Thank you for your feedback!

1. Am I correct with that you have a Stand-alone YouTrack? What version do you have?
This is a known issue and it's already fixed in current version. Is it possible for you to update your instance?
'Similar issues' option doesn't cause such behavior. For now, we have it's ON by default, but we're ready to concern the OFF option for future releases.


2. Frankly speaking, you're the first user who concerned this. So, you would like to see orange button's action other then 'Create issue', correct? In this case, it's better to change the bleu button's name.

Thank you.
0
Comment actions Permalink
Thanks for your help!

1. We're on the cloud version (last I checked 5.0.5 build 7537).  I don't have any concern with the 'Similar Issues' feature except that there appeared to be a correlation between the similar issues list appearing and when the characters tended to drop.  If that didn't happen then I think the current behavior of having a hide button is enough for anyone who dislikes it.

2. It's more a concern about the orange button's behavior of dismissing the new issue page while still being labeled 'Create Issue'.  There are two buttons with the same label text which do very different things in the same context.  The original source of the concern was that a couple people said that several times when they tried to create issues it turned out that they hadn't been committed.  I hadn't personally ever seen that behavior, but working with them we had the hypothesis that maybe they had clicked on the orange button in order to try to commit.  If that's the reason why the issues appeared to be abandoned it seems like this isn't a super big deal, and there are several reasonable ways to fix it if you chose to (change the blue button's label, change the orange button's label when on the new issue dialog, change the orange button's behavior when on the new issue dialog, etc.).
0
Comment actions Permalink
Joe,

1. The frequency it is reproduced? What browser?

2. Thank you for detailed use case. I think we'll consider this for future implementations. I guess it hasn't ever bothered other users because most of them use shortcut (ctrl + Enter (Mac)) for such actions.
In case it may be helpful for you, the list of shortcuts is available under question mark (top right corner of the page).

Thank you.
0
Comment actions Permalink
1. I can get it to repro basically 100% of the time.  I just need to vary the cadence of typing in the summary.  If I type consistently quick enough or slow enough it doesn't happen.  I'm generally seeing it in Chrome on Windows 7, but I've seen it also on Mac.

In case it's pertinent, we also have several custom workflows being applied to issues.  I don't know when the stateless rules get run over an issue.

2. I'll pass along the link for shortcuts.  Thanks for the pointer!
0
Comment actions Permalink
Joe,

Please, provide me with the list of workflows attached to a project. Is it reproduced with all projects or with that one to which the workflows are attached?
I'm trying to repro this, but no luck yet.
0
Comment actions Permalink
I started disabling some of our workflows one at a time and I found the one that seems to be problematic:

Workflow
rule Description template for new issues 
 
when !isReported() || Type.changed { 
  var bugTemplate = "===Steps to Reproduce:===\n" + "# First thing I did.\n# Second thing.\n# ...\n\n" + "===Expected Results===\n" + "What should have happened.\n\n" + "===Actual Results===\n" + "What did happen."; 
  var taskTemplate = ""; 
  var storyTemplate = "As a <type of user>, I want <some goal> so that <some reason>."; 
   
  if (description.isBlank || description.eq(bugTemplate, ignoreCase) || description.eq(taskTemplate, ignoreCase) || description.eq(storyTemplate, ignoreCase)) { 
    if (Type == {Bug}) { 
      description = bugTemplate; 
    } else if (Type == {Task}) { 
      description = taskTemplate; 
    } else if (Type == {Story}) { 
      description = storyTemplate; 
    } 
  } 
}
prettyPrint();

I'm surprised it's having the behavior of modifying the Summary, but disabling it fixes the dropped characters.  I don't know that it's not aggravated by the rest of our workflows.  If you're interested I can send you the full list.

I know there's this https://github.com/JetBrains/youtrack-workflows/tree/master/New%20Issue%20Description%20Template that does basically the same thing.  I'll try updating the workflow to mitigate the behavior.

Thanks for your help!
0
Comment actions Permalink
String comparisons are expensive.  Changing it to the following kept the behavior I wanted and seems to have addressed the performance problems:

rule Description template for new issues

when !isReported() || Type.changed {
  var bugTemplate = "===Steps to Reproduce:===\n" + "# First thing I did.\n# Second thing.\n# ...\n\n" + "===Expected Results===\n" + "What should have happened.\n\n" + "===Actual Results===\n" + "What did happen.";
  var taskTemplate = "";
  var storyTemplate = "As a <type of user>, I want <some goal> so that <some reason>.";
   
  if (Type.changed) {
    if (description.isBlank || description.eq(bugTemplate, ignoreCase) || description.eq(taskTemplate, ignoreCase) || description.eq(storyTemplate, ignoreCase)) {
      if (Type == {Bug}) {
        description = bugTemplate;
      } else if (Type == {Task}) {
        description = taskTemplate;
      } else if (Type == {Story}) {
        description = storyTemplate;
      }
    }
  } else if (description == null) {
    if (Type == {Bug}) {
      description = bugTemplate;
    } else if (Type == {Task}) {
      description = taskTemplate;
    } else if (Type == {Story}) {
      description = storyTemplate;
    }
  }
}
0
Comment actions Permalink
Apparently I spoke too soon.  It still repros with the workflows I have applied, but not as consistently now that I modified that particular one.  I am going to try to make the others more scoped for when they get applied so this won't happen.

Are there any kind of profiling tools or logs I can grovel to try to diagnose which workflows may still be problematic?

But that this is happening at all, even in the presence of a non-performant workflow, still seems like a bug in YouTrack, yeah?

Thanks again for any help with this.
0

Please sign in to leave a comment.