home.social

Search

1000 results for “jq”

  1. I think I'm too dumb to understand #JIRA API permissions...
    I want to access:
    /rest/api/3/issue
    /rest/api/3/search/jql

    The docs say I need:
    read:issue-details:jira
    read:audit-log:jira
    read:avatar:jira
    read:field-configuration:jira
    read:issue-meta:jira
    write:issue:jira
    write:comment:jira
    write:comment.property:jira
    write:attachment:jira
    read:issue:jira

    But when I run against the API with the token it fails. When I'm doing the same call with an unscoped api token it works. What do I do wrong!?

  2. I think I'm too dumb to understand #JIRA API permissions...
    I want to access:
    /rest/api/3/issue
    /rest/api/3/search/jql

    The docs say I need:
    read:issue-details:jira
    read:audit-log:jira
    read:avatar:jira
    read:field-configuration:jira
    read:issue-meta:jira
    write:issue:jira
    write:comment:jira
    write:comment.property:jira
    write:attachment:jira
    read:issue:jira

    But when I run against the API with the token it fails. When I'm doing the same call with an unscoped api token it works. What do I do wrong!?

  3. I think I'm too dumb to understand #JIRA API permissions...
    I want to access:
    /rest/api/3/issue
    /rest/api/3/search/jql

    The docs say I need:
    read:issue-details:jira
    read:audit-log:jira
    read:avatar:jira
    read:field-configuration:jira
    read:issue-meta:jira
    write:issue:jira
    write:comment:jira
    write:comment.property:jira
    write:attachment:jira
    read:issue:jira

    But when I run against the API with the token it fails. When I'm doing the same call with an unscoped api token it works. What do I do wrong!?

  4. I think I'm too dumb to understand #JIRA API permissions...
    I want to access:
    /rest/api/3/issue
    /rest/api/3/search/jql

    The docs say I need:
    read:issue-details:jira
    read:audit-log:jira
    read:avatar:jira
    read:field-configuration:jira
    read:issue-meta:jira
    write:issue:jira
    write:comment:jira
    write:comment.property:jira
    write:attachment:jira
    read:issue:jira

    But when I run against the API with the token it fails. When I'm doing the same call with an unscoped api token it works. What do I do wrong!?

  5. I think I'm too dumb to understand #JIRA API permissions...
    I want to access:
    /rest/api/3/issue
    /rest/api/3/search/jql

    The docs say I need:
    read:issue-details:jira
    read:audit-log:jira
    read:avatar:jira
    read:field-configuration:jira
    read:issue-meta:jira
    write:issue:jira
    write:comment:jira
    write:comment.property:jira
    write:attachment:jira
    read:issue:jira

    But when I run against the API with the token it fails. When I'm doing the same call with an unscoped api token it works. What do I do wrong!?

  6. #Jira is such high-quality, professional web software, that it will show a page title that has nothing to do with the URL.

    Case in point, i have in my history an entry for the following URL:
    mycompany.atlassian.net/issues

    but it has the following page title:
    [TEAM-2021] Other Unrelated Customer ticket title

    So now, when i search for Other Unrelated Customer, i can "conveniently" be taken to search results for CustomerA. Truly a great user experience.

  7. #Jira is such high-quality, professional web software, that it will show a page title that has nothing to do with the URL.

    Case in point, i have in my history an entry for the following URL:
    mycompany.atlassian.net/issues

    but it has the following page title:
    [TEAM-2021] Other Unrelated Customer ticket title

    So now, when i search for Other Unrelated Customer, i can "conveniently" be taken to search results for CustomerA. Truly a great user experience.

  8. #Jira is such high-quality, professional web software, that it will show a page title that has nothing to do with the URL.

    Case in point, i have in my history an entry for the following URL:
    mycompany.atlassian.net/issues

    but it has the following page title:
    [TEAM-2021] Other Unrelated Customer ticket title

    So now, when i search for Other Unrelated Customer, i can "conveniently" be taken to search results for CustomerA. Truly a great user experience.

  9. #Jira is such high-quality, professional web software, that it will show a page title that has nothing to do with the URL.

    Case in point, i have in my history an entry for the following URL:
    mycompany.atlassian.net/issues

    but it has the following page title:
    [TEAM-2021] Other Unrelated Customer ticket title

    So now, when i search for Other Unrelated Customer, i can "conveniently" be taken to search results for CustomerA. Truly a great user experience.

  10. #Jira is such high-quality, professional web software, that it will show a page title that has nothing to do with the URL.

    Case in point, i have in my history an entry for the following URL:
    mycompany.atlassian.net/issues

    but it has the following page title:
    [TEAM-2021] Other Unrelated Customer ticket title

    So now, when i search for Other Unrelated Customer, i can "conveniently" be taken to search results for CustomerA. Truly a great user experience.

  11. In meiner swaybar (die Leiste, die #sway haben kann), habe ich ein Scratchpad, das isr der Bereich, in den ich alle Fenster werfen kann, die ich momentan nicht sehen will.
    Die Bar wird von einem Shellskript gebastelt, das für das Scratchpad diese Funktion hat:

    get_scratchpad() {
        windows=$(swaymsg -t get_tree | jq -r '
            .. | objects
            | select(.name? == "__i3_scratch")
            | .floating_nodes[]
            | (.app_id // .window_properties.class // .name)
            | if test("^\\..*\\.bin$")
              then sub("^\\."; "") | sub("\\.bin$"; "")
              else .
              end
        ')
    
        if [ -z "$windows" ]; then
            echo "Scratchpad: empty"
        else
            echo "Scratchpad: $(echo "$windows" | paste -sd " ") |"
        fi
    }

    Ergibt momentan:

    Ohne #ChatGPT hätte ich das im Leben nicht hinbekommen, #jq ist zwar mächtig, aber auch hart.

  12. In meiner swaybar (die Leiste, die #sway haben kann), habe ich ein Scratchpad, das isr der Bereich, in den ich alle Fenster werfen kann, die ich momentan nicht sehen will.
    Die Bar wird von einem Shellskript gebastelt, das für das Scratchpad diese Funktion hat:

    get_scratchpad() {
        windows=$(swaymsg -t get_tree | jq -r '
            .. | objects
            | select(.name? == "__i3_scratch")
            | .floating_nodes[]
            | (.app_id // .window_properties.class // .name)
            | if test("^\\..*\\.bin$")
              then sub("^\\."; "") | sub("\\.bin$"; "")
              else .
              end
        ')
    
        if [ -z "$windows" ]; then
            echo "Scratchpad: empty"
        else
            echo "Scratchpad: $(echo "$windows" | paste -sd " ") |"
        fi
    }

    Ergibt momentan:

    Ohne #ChatGPT hätte ich das im Leben nicht hinbekommen, #jq ist zwar mächtig, aber auch hart.

  13. In meiner swaybar (die Leiste, die #sway haben kann), habe ich ein Scratchpad, das isr der Bereich, in den ich alle Fenster werfen kann, die ich momentan nicht sehen will.
    Die Bar wird von einem Shellskript gebastelt, das für das Scratchpad diese Funktion hat:

    get_scratchpad() {
        windows=$(swaymsg -t get_tree | jq -r '
            .. | objects
            | select(.name? == "__i3_scratch")
            | .floating_nodes[]
            | (.app_id // .window_properties.class // .name)
            | if test("^\\..*\\.bin$")
              then sub("^\\."; "") | sub("\\.bin$"; "")
              else .
              end
        ')
    
        if [ -z "$windows" ]; then
            echo "Scratchpad: empty"
        else
            echo "Scratchpad: $(echo "$windows" | paste -sd " ") |"
        fi
    }

    Ergibt momentan:

    Ohne #ChatGPT hätte ich das im Leben nicht hinbekommen, #jq ist zwar mächtig, aber auch hart.

  14. 🚀 Wow, #jsongrep is faster than jq? Alert the media! 📣 After a mere 17-minute read filled with mind-numbing automata theory and #benchmark babble, you'll finally learn that using jsongrep will save you a whopping nanosecond per query. 💤 Meanwhile, the rest of us will continue to use #jq, blissfully unaware of this groundbreaking revelation. 🙄
    micahkepe.com/blog/jsongrep/ #automation #performance #tech #news #HackerNews #ngated

  15. 🚀 Wow, #jsongrep is faster than jq? Alert the media! 📣 After a mere 17-minute read filled with mind-numbing automata theory and #benchmark babble, you'll finally learn that using jsongrep will save you a whopping nanosecond per query. 💤 Meanwhile, the rest of us will continue to use #jq, blissfully unaware of this groundbreaking revelation. 🙄
    micahkepe.com/blog/jsongrep/ #automation #performance #tech #news #HackerNews #ngated

  16. 🚀 Wow, #jsongrep is faster than jq? Alert the media! 📣 After a mere 17-minute read filled with mind-numbing automata theory and #benchmark babble, you'll finally learn that using jsongrep will save you a whopping nanosecond per query. 💤 Meanwhile, the rest of us will continue to use #jq, blissfully unaware of this groundbreaking revelation. 🙄
    micahkepe.com/blog/jsongrep/ #automation #performance #tech #news #HackerNews #ngated

  17. 🚀 Wow, #jsongrep is faster than jq? Alert the media! 📣 After a mere 17-minute read filled with mind-numbing automata theory and #benchmark babble, you'll finally learn that using jsongrep will save you a whopping nanosecond per query. 💤 Meanwhile, the rest of us will continue to use #jq, blissfully unaware of this groundbreaking revelation. 🙄
    micahkepe.com/blog/jsongrep/ #automation #performance #tech #news #HackerNews #ngated