Vitalii Rybka Specialist

Welcome to the community!🫰

@Palo Otčenáš that's a good point. I currently use Claude Code + Atlassian MCP + Skills. Much better results. BTW, what skills are you looking for?

Nicely done. It wouldn't be so funny unless there were so many such examples. I hope Jira Service Management (JSM) will help to improve the situation. My best "scary backlog story" is: - All the bugs that aren't fixed before the New Year are becoming features. BTW, does your project use Forge? If so, I would like to get…

Sounds strange. Did you try to check what returns issueLinks.FILTER()? As far as I understand, issueLinks returns link objects, not issue objects directly.

Hi @Yvette Nash, The issue you're facing is probably because of how Structure formulas handle the statusCategory property. In Structure formulas, you have to access the status category differently from JQL. Here are a few approaches to try: * issueLinks.FILTER($.type = "Risks" AND $.status.statusCategory.name != "Done") *…

Hey @Noah Leu -MESKRU GmbH-, It looks like something went wrong. I have tried your script and even added a new column. Everything worked as expected (attached screenshot). Please check compatibility with your current version of Cloud. Or report an issue to the vendor team. Best, Vitalii

Yay! My congrats! As usual, a side effect change has fixed the issue ;-)

Sounds pretty weird. I believe you should try a very simple request with only one field. Here is an example from the docs: # This code sample uses the 'requests' library: # http://docs.python-requests.org import requests from requests.auth import HTTPBasicAuth import json url =…

@Garrett Kaufmann, I would like to clarify. Do you use Forge env or Node.js env? According to the docs, there are several important notes: * If the JQL query expression is too large to be encoded as a query parameter, use the POST version of this resource. * Permissions required: Issues are included in the response where…

In Jira Cloud Scriptrunner, Behaviors are limited vs Server/DC you can’t fully hide/show fields, only set them required/optional or read-only; for onChange you can check the select value and then use setHidden(true/false) in code, but since it’s not fully supported in Cloud, the workaround is using Forms, Forge apps, or…

I’ve seen this before in my opinion it’s a cache/sync issue on the Google Sheets side; try reinstalling after clearing cache, use the filter ID from the Jira URL instead of the name, wait a few hours for sync, and if that doesn’t work, raise a ticket with Atlassian support.

I think the issue might be with the fields or expand parameters - in the v3 API you often get an empty array if no fields are specified. Try adding something like fields=summary,key (or whichever fields you need), and the response should start returning data.

Yay! Thanks, @Angelie Stephens, for tagging me. Let's go to the next milestone ✍️

Hi @Udaya Sri! Congrats on joining! Can't wait to see more posts from you ;-) Warm regards, Vitalii

Hi Joao Vitor Rodrigues Da Silva, I think the issue might be with the endpoint path or the base URL not matching the correct environment (production vs. test). I recommend double-checking the API documentation for the exact endpoint and ensuring the headers are set correctly. If the problem persists, consider reaching out…

Hi @krishna_h_dixit - yes, you can create custom "Test Request" issue types in Jira with workflows for lab managers to submit requests, get approvals, and track execution through completion.

I think you can do it in one IFTTT using: "components":[{"name":"[entry.Field_A]"},{"name":"[entry.Field_B]"}<#if entry.Field_C != "C3">,{"name":"[entry.Field_C]"}</#if>] – this includes Field_C only when it’s not C3.

I have a hunch the issue comes from changing both the Issue Type and Request Type at once – try updating the Issue Type first, then use a Re-fetch action, and only after that change the Request Type, or split it into two separate rules.

Hi @Mantas Viržintas, This is a common issue during the Atlassian account migration process. Here's what you should do: Immediate Steps: * Contact Atlassian Support directly at https://support.atlassian.com - they can help merge accounts or recover your original boards * Don't delete either account until Support resolves…

Hi @Colton_Kosicek, This sounds like a Rovo agent permission issue when trying to access child issues. Here are some troubleshooting steps: Check These First: * Agent Permissions: Ensure the agent has access to the project containing the child stories * Issue Type Permissions: Verify the agent can access Story issue types,…

Hi @Melissa C, You're on the right track! Here's a cleaner approach to detect multiple Q versions and set "Needs Attention": Solution: handlebars<span>{{#with(triggerIssue.fixVersions.where(name.contains("Q")))}}</span><span> {{#if(size.gt(1))}}</span><span> Needs Attention</span><span> {{else}}</span><span>…

Hi @Allison Mease, Perfect! For Tracking and Estimation for Jira Cloud, here's the specific approach: Smart Value for Assignee by Role Field: The plugin typically stores role assignments in a custom field. Try these smart values: * {{issue.customfield_XXXXX.accountId}} - if it stores account IDs *…

Hi @Matthew Musgrove, Good catch! You're absolutely right - EB deployments often trigger CloudFormation, Auto Scaling, and EC2 operations behind the scenes. The AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy is a solid approach. Alternative Managed Policies to Consider: * AWSElasticBeanstalkWebTier - for web server…

Hi @S Fong, The "add-on disabled" issue is usually related to admin permissions or app configuration. Here's how to troubleshoot: Check These First: * Admin Rights: Ensure you have Jira admin permissions (not just Confluence admin) * App Status: Go to Jira Settings > Apps > Manage apps and verify the Microsoft Teams…

Hi @Allison Mease, Welcome to the community! You can definitely achieve this with automation rules. Here's how to handle both scenarios: For Project-Specific Role-Based Assignment: Create an automation rule with: * Trigger: Issue created/transitioned * Condition: Project equals "Your Project Name" * Condition: Check if…

Hi @Matthew Musgrove, For the atlassian/aws-elasticbeanstalk-deploy:1.5.0 pipe with OIDC, you'll need these minimum IAM permissions: Essential Permissions: json<span>{</span><span> "Version": "2012-10-17",</span><span> "Statement": [</span><span> {</span><span> "Effect": "Allow",</span><span> "Action": [</span><span>…

Hi @Florian Bonniec, @Tomislav Tobijas is correct - this is expected behavior for security reasons. Here are a few workarounds: Option 1: Service Account Approach * Create a dedicated service account with broader project role memberships * Use this account for filter sharing operations * Add it to all relevant project…

Hi @Henry hvconrail, As @[deleted] mentioned, Jira's private/internal APIs aren't meant for external access - they're browser-session specific and unsupported. Alternative Solutions for Commit Data: * Jira REST API with Development Information:* Use /rest/api/3/issue/{issueKey}?expand=changelog * Look for development…

Hi @Susan Cain, Here are a few troubleshooting steps for sprint assignment automation: Common Smart Values for Sprints: * {{sprint.name}} - for sprint name * {{sprint.id}} - for sprint ID * {{issue.sprint.name}} - current issue's sprint name Things to Check: * Sprint State - Make sure the target sprint is in "Active" or…

Hi @Joshua Robinson, While Marc's approach works, you actually have several options beyond creating separate CIs: Option 1: Environment-Version Attributes Add custom attributes like "Prod_A_Version", "Prod_B_Version", "Prod_C_Version" to your Terraform CI. This tracks version drift in one object. Option 2: Deployment…