Nir Haimov Community Champion

You can follow this guide, how to do it form the UI https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html General tip, know how the app work from the UI, than go for API

Hi, You need to send a POST call to: https://your_jira_url/rest/api/2/issue/{issueKey}/comment add header: "Content-Type", "application/json" your body data should be like: { "body": "{code:java}// code placeholder{code}" }

OK, replace the "branch rule", after "When" create new condition "Related issues condition": Related issues = Linked issues Condition = None match JQL JQL = Status in ("Awaiting for Approval") Then: do what you want

It's hard without seeing what you are dealing with, but you need to use "Branch rule / related issues" to achieve this

Hi, Check your project permissions, and make sure you have "View Development Tools" permissions

403 usually means you have no permission to do that change. Do you have permission to change schemes through the UI?

You can go one by one and look at the ticket history to see what was the field value before. Or code something that will do the same for you.

Hi, You can do that, but you will need 3rd party plugin (don't think you can do all of this without a plugin), the easiest one I think will be: https://marketplace.atlassian.com/apps/1215460/automation-for-jira?hosting=cloud&tab=overview

Hi, What you are describing sound like what you want is to prevent ticket to move from, status to status on a certain condition. So you can add "condition/validation" in the workflow

Hi @YUVARAJ KUNDASI Sorry but, You can't do that from the REST API.

@[deleted] Found out that for me it was just that I missed to add my JS module to the download resources. I am familiar with the version in pom.xml and caching thing :) Good to know you figured that out and solved your issue too.

You can do that by putting "sub-task" under separate workflow. Than add the entire workflow status with property: jira.permission.edit.role=your_role

You will have to use a 3rd party plugin, "Automarion for Jira" will do the trick. https://marketplace.atlassian.com/apps/1215460/automation-for-jira?hosting=cloud&tab=overview Or, you will have to code something to do it.

I will suggest you to simply use different browser than IE11. Even if you will solve this now, Atlassian already announced that they will not support IE11 as of March 31, 2020 https://blog.developer.atlassian.com/retiring-ie11-support-for-atlassian-cloud-server-and-data-center-products/ So just get used to work with…

Exactly :)

Hi, When you create issue via REST API the issue will always be at it first status "New". If you want it to be in "In Progress" you have to transition the issue to that status, using this: POST /rest/api/2/issue/{issueIdOrKey}/transitions Body of your post will be: "transition": { "id": "5" } *replace 5 with your relevant…

I don't think you can add all comments at once. But you can run in a loop trough all comments and add then one after one

Use http://mydomain:port/rest/agile/1.0/board/{boardId}/project Returns all projects that are associated with the board, for the given board Id. A project is associated with a board only if the board filter explicitly filters issues by the project and guaranties that all issues will come for one of those projects e.g.…

Hi @[deleted] Have you find any solution for this? I just got into the same problem, actually i created 3 gadgets already and they work fine, but now the forth giving the exact same error as you had.

Hi, Are there any additional errors in the logs? Maybe the users exist twice? Check also in the database records that the user not exist twice (not only from the UI)

Hi, It's possible with the paid version, not the free version: Paid - https://marketplace.atlassian.com/apps/1215460/automation-for-jira?hosting=cloud&tab=overview Free - https://marketplace.atlassian.com/apps/1215670/automation-for-jira-cloud-lite?hosting=cloud&tab=overview

Hi, You have notification scheme https://confluence.atlassian.com/adminjiracloud/creating-a-notification-scheme-776636401.html What ever you set is apply to all relevant project issues. It's not modified per created ticket.

Transition Screen: https://confluence.atlassian.com/jirakb/mapping-a-screen-to-a-workflow-transition-720634253.html Transition Condition: https://confluence.atlassian.com/adminjiraserver/advanced-workflow-configuration-938847443.html

Hi, If I understand right, you have another system them hold the data about available spots... So you have to get the data from there everytime someone create a ticket. You can do it with Scriptrunner plugin or writing your own plugin. In both options, you will have to code this solution. No tool will just be able to…

Hi, You can't set a field to be editable only by specific someone. What you can do is (workaround): 1. Don't put the field in the "edit" screen 2. Create transition screen, put your field there, add validation that transition can't be complete without the field having a value, and condition that only the "Project Lead"…

Hi @Developer 1 , This work only in Jira Server, not Cloud, as in Cloud you can't use JS

This is the way to get it filtered and not getting all issues... It sounds weird you get all issues on and not only Sub-tasks (for me it works fine)

Did my line worked for you (for Sub-task)? What is the error you get, it should work for any issue type. of course if you want to filter multiple issue types at once, it should be: /rest/api/2/search?jql=assignee=currentuser() AND issuetype in (Sub-task, task, test)&fields=key,id,issuetype,project,subtasks,summary,status

Hi, Unfortunately, Jira does not come with Hebrew language package. Also, none created plugin for Jira to support RTL correctly for Jira. However, there is chrome extension someone created (if you are using chrome): https://chrome.google.com/webstore/detail/jirartl/djnbhcebgngagmioniajfhbldkoegcco Seems to do a good job

Hi, you can filter your search by issuetype name, not id. Your request should be: /rest/api/2/search?jql=assignee=currentuser%28%29%20AND%20issuetype=Sub-task&fields=key,id,issuetype,project,subtasks,summary,status