Mikal H Henriksen

My feedback

  1. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Structure for JIRA: Ideas » Structure  ·  Flag idea as inappropriate…  ·  Admin →
    Mikal H Henriksen shared this idea  · 
  2. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Structure for JIRA: Ideas » Structure  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mikal H Henriksen commented  · 

    Thanks for the quick reply, Igor! The REPLACE trick can do basically all I asked for, and even handles multiple capture groups :) And thanks for the tip about the flags. I'm familiar with Java's Matcher, so knowing that that's what's behind the curtain is a huge help.

    10/10 service A++++ would post idea again!

    An error occurred while saving the comment
    Mikal H Henriksen commented  · 

    I think it would need to be more flexible than just a fixed pattern like that. For example it would be fantastic to be able to capture release note text from description with a pattern like "h4\. Release Notes (.*-) h4\.", or pick out specific labels like "theme/(.*)" and "feedback (.*)"

    Dunno if you want to go for something simpler, than regular expression syntax, but it would be a really powerful tool to have, especially for fields that can have multiple values like links, labels, fix version etc.

    Mikal H Henriksen supported this idea  · 
  3. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Structure for JIRA: Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    Mikal H Henriksen supported this idea  · 
  4. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    accepted  ·  3 comments  ·  Structure for JIRA: Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    Mikal H Henriksen supported this idea  · 
  5. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Structure for JIRA: Ideas » Structure  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mikal H Henriksen commented  · 

    I just had a similar idea that might also look better for systems with a lot of varying types of links. What if there was a column that can show each link relation of the issue to the parent issue? That way we can simply extend an issue with all linked issues (or some custom filter), and expose the relation with the column instead of in the hierarchy.

    An error occurred while saving the comment
    Mikal H Henriksen commented  · 

    I'd like this too. We have a large organization with several teams and projects. My use case is to get an overview of all issues in other projects that are linked to my project, mostly to easily visualize blocks, but usage of link types isn't always consistent so I don't want to limit it to one link type. So that means all link types and directions, and I was picturing it as a subfolder per link direction, kinda similar to what it looks like on the normal issue details page.

    I'm handling it right now with ScriptRunner and an extender per link type, but it's a chore.

    Mikal H Henriksen supported this idea  · 

Feedback and Knowledge Base