Hana Kučerová Community Champion

Hi @Mark Duncan release name won't update in the filter automatically, you need to change it manually.

Hi @Alejandra , this is really weird, I believe your code should work. I've tested this code using console (with KEY = issue key and NAME = sub-task issue type name): import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.IssueManager import com.atlassian.jira.issue.Issue IssueManager…

Disabled automation rules don't count toward your usage, because no event is fired.

Hi @Gabrielle Walden-Alves , welcome to the Atlassian Community! It think the Usage tab could help you with this. I would recommend you to read these two articles - you will get all necessary info about usage, statistics and how the limit is counted.

Hi @Sharon Freij , how I imagine this functionality: 1) The main story is created, it's due date is empty 2) The first sub-task is created with due date 30. 4. 2021, there's no due date in parent, so the parent's due date is set to 30. 4. 2021 3) The second sub-task is created with due date 31. 3. 2021, this due date is…

@Lucille Gonzales Thank you. I think automation rule could help you with this. Something like: WHEN: Issue is created IF: JQL condition: created >= startOfDay() AND created < startOfDay(7h) THEN: Assign issue to user A ELSE IF: JQL condition: created >= startOfDay(7h) AND created < startOfDay(15h) THEN: Assign issue to…

Hi @Sharon Freij , welcome to the Atlassian Community! First idea - what about to react on the change of sub-task's due date? Something like - everytime the due date of sub-task is changed, find the parent and compare the dates. If the parent's due date is greater then the sub-task's due date, change the due date in the…

Hi @Volodymyr welcome to the Atlassian Community! I can see you are sending your request to API version 2, the format of the data is for the API version 3. So, please try to send POST request to URL: https://peolyintegromat.atlassian.net/rest/api/3/issue/10001/comment

Hi @Alejandra , please, just to be perfectly clear, how this should work... You want to check, if there's at least one subtask with type "Imputacion de Horas"? No matter which types the other possible subtasks have? Thank you.

Hi @Lucille Gonzales , please, how exactly do you mean this? Like: * if issue was created between midnight and 7 AM, issue should be assigned to user A. * if issue was created between 7 AM and 3 PM, issue should be assigned to user B. * if issue was created between 3 PM and midnight, issue should be assigned to user C. ?

This is great, I love it :-)

@Hari Prasath Please, try to ask somebody to give you information from the logs. This error message is not enough to determine, what's going on.

Hi @Hari Prasath , thank you. Are you able to check the logs? It seems to me, it could be this problem.

Hi @Giuseppe Amoruso , I strongly believe this won't work - it will use the the first available comment (it won't have any connection to the Processing status). Maybe some other idea... 1) Create datetime custom field 2) Create the first rule, which will react on issue transition. If issue is transitioned to the status…

Hi @Dawn Rodney , please, how does your script look like - which test script did you use? Thank you.

Hi @Hari Prasath , welcome to the Atlassian Community! Please, would you provide more information about your problem? It is not clear what you are trying to achieve, where you get this error message etc. Thank you.

Hi @Joey Klein , I would use default report functionality in JSM project. You can setup Time to resolution SLA and based on this SLA you can create your custom report with series: Time to resolution (avg.)

Hi @Firas hammami , please, what do you mean by you don't have any output? What I was trying to say is that you need to deactivate two different groups of users. How does your code looks like now? Thank you.

Me too :-)! Thank you @Ben Thoma !

Hi @Jacob Francois , the problem is - it is not easy to determine, which boards are connected to the project. See this question, there are some useful information.

Hi @Firas hammami , according to this script the condition !loginManager.getLoginInfo(it.username).lastLoginTime looks ok. I think the problem is you are later checking last login, but these users don't have any. So these users won't get through the condition: if (lastLoginMillis?.isNumber()) {

Hi @Ahmad Sidawi , I believe you don't need to iterate through the users, you can just add smart value: {{issue.Your custom field name}}

There will be a lot of changes with Jira Work Management, next generation of Jira Core (Timeline ~ Gantt will be available and much more). Hopefully we will get this soon...

Hi @Marius Suta , welcome to the Atlassian Community! I believe this functionality is available only for software classic projects, not business (Core). Boards in business projects are very limited, see here.

Hi @Marcelo Maia da Silva , welcome to the Atlassian community! According to the Supported Platforms article it is not supported, only SQL Server 2017.

Is the page from different space or not? Sorry, I didn't assume you're linking between two spaces.

Looks like you are on server, there's no "atlassian.net" in the confluence URL, right? There are two steps. 1) create the anchor using macro (I've created anchor with name "my anchor" on the page "Test page") 2) navigate to the other page, where you want to have your link and during inserting link go to the "Advanced"…

Hi @Beetle Admin , you need to be Organization Admin to be able to get to those sections, see for example here for the basic explanation. Could it be that the removed user was Organization Admin? I would normally recommend you to contact Atlassian support, but since you're on free product plan, this option is not…

Hi @Wemmie , welcome to the Atlassian Community! The instruction you provided is for the server Confluence, but you've tagged your question with "cloud". Please look here for the cloud version of the article (section Link to an Anchor macro on another page).

I can't wait to start using it. It looks fantastic! Thank you!