Ignacio Vera Specialist

Hi @Andrew Coutermarsh Try using a codeBlock node instead of paragraph in your ADF, with language set to yaml. That prevents Jira from applying Smart Linking to the email. Something like this: description: type: doc version: 1 content: - type: codeBlock attrs: language: yaml content: - type: text text: | Name:…

hi @sumit patidar try from filters -> search work items -> change if needed to JQL and search: parent = SYM-6047 and search. then go to the three dots at the right corner and click on bulk change work items. please let me know if that works

you can if you have a borad as template and use greenHopper, but is not the most reliable option

You need to set the rule as global or multiple projects (and select all the affected projects)

I use Revyz, but creates duplicated stuff sometimes. The cleanest solution? do it manually The fastest? use revyz or configuration manager plugins

@Mykenna Cepek I’ve made some progress, but I think there’s a bug on the ServiceNow side. When authorizing the OAuth token with the org admin account, the page redirects to the Groups screen rather than the authorization confirmation page.

@Mykenna Cepek 

OMG, what are the odds? I have to do the same now Did you made it work??

hi @Kumari Dvipa If the other site is brand new and blank, this is your best option. Otherwise you will get duplicated stuff like custom fields, screens, etc, but nothing that a painful clean up can't fix. Another option is revyz, that mostly the best option for active target instances

Hi @Zeker Nazari I don't understand if your going to use JSM or Jira. But if you use JSM, internal tickets are not visible by customers. You can even comment internally tickets that are shared with customers. If you are planning to use Jira and users (customers) have complete access to the project, you can use a security…

This is expected behavior according to Atlassian’s documentation: The Create Issue endpoint explicitly states that only fields present on the Create screen can be set. The Edit Issue endpoint allows updates to fields determined by the “Get edit issue metadata” endpoint and even includes parameters (overrideScreenSecurity,…

Hi @Saif Allah AZZAZA I would manage this with two rules. First rule: Trigger: Issue transitioned --> To Done Branch: Parent Actions: Re-fetch issue data Edit issue fields --> Story/task field = {{issue.subtasks. filter(s => s.status.name =="Done").sum(customfield_12345)}} Rule 2 (optional, when subtask leaves Done):…

Are you referring to the ones you created in the Admin Hub? If so, which scope did you select for that service account? That could be causing the issue.

Hi @Maria João Lima Your Xray issues (Tests, Test Plans, Executions) will remain in Jira after unsubscribing because are Jira issues. You can still view and search them using Jira filters. Xray-specific panels, reports, and fields will no longer work, so I suggest exporting your test data before unsubscribing, just in…

Hi @Emily C. You can hide resolved ticket * Next to your plan’s name in the sidebar, select More actions (•••), then Plan settings. * Select Work in your plan, then select Removed work items. * Select View rules. * In the panel that opens, select the box under Remove work marked DONE more than and enter your preferred…

Hi @Dejan Stajic The pagination behavior in v3 changed Try using the startAt parameter instead of relying on nextPage, for example: /rest/api/3/search?jql=filter=12345&startAt=100 Loop until isLast is true. That usually avoids the duplicate-page issue with Power BI connectors.

It doesn't work. You cannot create issues without the Browse permission

There’s no built-in “write-only” API user in Jira Data Center. I suggest you to use an intermediary service that only forwards specific “create/update” operations to Jira via REST, and that way you can be sure you are not exposing read endpoints back to monday.com

I’d recommend checking whether the userAccountControl attribute is configured in your Jira Data Center LDAP directory settings. Jira relies on that attribute to detect whether an AD user account is disabled.

Hi @Bunny My suggestion is that if you’re not 100% sure how to do it, hire a partner to handle the migration. If the budget doesn’t allow that, I recommend doing it all at once and involving a few key users for testing. Migrating 5k tickets is not considered a complex migration, especially since you only mentioned Jira.…

Hi @Paula Cruickshank Yes. There is an active incident http://status.atlassian.com/

@Marcelo Viana de Siqueira The jira.permission.create property doesn’t control who can create new issues, it only applies to actions performed on existing issues once they’re already in that status (for example, creating sub-tasks) If your goal is to restrict who can create new issues, you can add a condition or validator…

Is the default language for that Jira Cloud site set to Chinese?However, since this is an authentication (401) error, it might just be falling back to Chinese for some reason when the request isn’t authenticated.Could you check what happens when the response is 200 — is it still in Chinese, or only the errors?

As I said, {{issue.parent.fields.Team}} works. It returns the teams id, which you need to update the teams field.

You don't need JSON. Is not a custom field. 

Your rule is almost correct. The main problem is the smart value, because timeoriginalestimate is stored in seconds and 6h is not valid syntax in Jira expressions. Try this: In the “Create variable” action, set calculatedDueDate to: {{issue.Start Date.plusDays( issue.timeoriginalestimate.divide(3600).divide(6).toNumber )}}…

You can edit the created task like this: Action: Edit issue fields → select the Team field. In the value, enter: {{issue.parent.fields.Team}} This makes the task automatically inherit the Team field from the parent.

Please show us the Permission scheme. The other users that were ablet to create, where in a different role than Developers?

Hey Seba! Try this Trigger: Incoming webhook Create variable: ticketId = {{webhookData.ticketID}} Lookup issues: project = ABC AND "Some text field" ~ "{{ticketId.escapeJql}}" IF {{lookupIssues.size}} = 0 Create issue: Summary: {{webhookData.title}} Description: {{webhookData.description}} Some text field: {{ticketId}}…

Hey! Are you using Jira cloud? You should see the choose the background color below