Gor Greyan Expert

Hi @Shelby Rosten Did you put the "Prevent duplicates by only adding this comment once to a particular work item." checkbox as ticked, like in the attached screenshot? It checks the target issue. If the same comment text already exists, Jira skips adding it again. If the comment does not exist yet, it adds it normally.

Hi @Michael Green Thanks for the question. Jira's date format is controlled by Jira’s own locale settings, not your computer’s. I think you could change it in the Look and Fill section, but this impacts all users. Check it in this section. https://yourdomain.atlassian.net/secure/admin/LookAndFeel!default.jspa

Hi, @Tejaswini Dilip Patil Unfortunately, still can't see the screenshots.

Hi @Eliya Sarfarti Thanks for the question. Did you put the Branch rule after the ticket creation in the Company Managed project? Also, if you could provide a screenshot of the automation structure, it will be easier for me to help you.

Dear @Tejaswini Dilip Patil Seems the screens are not attached, it is not visible for me.

Dear @Tejaswini Dilip Patil Thanks for the answer. Could you please share a screen from the Columns page?

Hi @Tejaswini Dilip Patil Welcome to the Atlassian Community! Firstly, I would ask which type of project it is that, where the + button is not visible, Team-Managed or Company-Managed?

Hi @Nancy Stankovich Welcome to the Atlassian Community! Jira’s native issue types are restricted to a 3-level hierarchy. Sub-tasks are the bottom level, and Jira doesn’t allow creating any children under them, regardless of issue type. I think you can do this with this solution. If you want the bug to “live” within the…

Hi Dear @John Funk One question also :) I want to set automation so that when my Design task goes to Done status, the issue in the Parent Link goes to "In Progress" status. In the automation, for the branch I set Epic(parent), but the Parent is not being recognized as Parent :D Do you have any idea?

Hi @John Funk Thanks a lot for the answer.

Hi, Dear @John Funk See, for the default Epic issue type, I have a Summary Panel section in the right part, which shows how many tickets are completed under that epic, estimation and etc. For the new Epic level issue type, I couldn't see that information. See the attached screenshots.

Hi @John Funk I could link it via Parent Link, but I want the child issues' estimations will be visible also in this Parent. Now it is not visible. How can we also do that? Like the Summary Panel, which is visible in the Epic.

Hi @arielei I have found another simple solution, via the conditions. I put 2 conditions. 1. {{issue.customfield_11735.size}} is grather than 0 2. {{issue.Partner.value.join("|")}} exactly matches the Regular Expression, and my Partner names with Reg-ex. This worked.

Hi @John Funk Thanks for the answer. But couldn't find the Parent field. With the Parent name, we have only this fields.

Dear @Aleena Umaiir If this also helps and works, kindly ask you accept the answer.

Hi @Aleena Umaiir Welcome to the Atlassian Community! I will suggest another version also. Again, Use Jira Automation. See the attached screen and use the following. Replace the XXXXX with the ID of your field. { "fields": { "customfield_XXXXX": "{{#=}} issue.customfield_XXXX + 1 {{/}}" } }

Dear @Nikola Perisic I could link it via Parent Link, but I want the child issues' estimations will be visible also in this Parent. Now it is not visible. How can we also do that? Like in the Epic, Summary Panel.

Hi @Eric Roetenberg You can use the following smart value, putting in the Receipts fields. See also this article. https://confluence.atlassian.com/automationkb/automation-for-jira-how-to-write-a-rule-that-will-send-an-email-to-the-project-lead-1456345479.html

Hi @arielei Thanks for the answer, but as I mentioned, I can't exclude the rest values, as I have more than 100 values, and it is being added again and again.

Hi @Glenn_Riley1 See the attached screen; it should look like this.

Hi @Nikola Perisic I have added a ticket in the Epic hierarchy level. I have created a ticket with the Epic Name field, but in another ticket, when I entered the Epic Link and wrote the Epic's name, it did not suggest that Epic. Please see the screens.

Hi @Amandeep Kaur Butar Welcome to the Atlassian Community! Could you please provide more detailed information on what you want to use?

Dear @Glenn_Riley1 Inside the branch, before the edit action, add condition summary ~ "ATTACH XML", it will do only for that sub-task. I will also provide screenshot tommorow.

Dear @Glenn_Riley1 Sure, see the attached screenshot. You should choose a set, not the copy, and put the smartvalue.

Hi @Glenn_Riley1 Welcome to the Atlassian Community! You can do that via this automation. Instead of copy value from the parent, you can use the smart value {{issue.parent.duedate}}, as also @arielei stated above. Also, you can change the Trigger. If it should be sub-task creation, you can remove the branch part and only…

Hi @Nikola Perisic Thanks a lot. Will check and get back to you.

Hi @[deleted] Thank you for your feedback)) First, I didn't notice that the post was made in 2020. Second, I didn't state that this 1is 00% working, I said that I found that. Third, you can be sure that I am testing it when providing a solution; otherwise, I don't state that it is working. Have a good day.

Hi @Nikola Perisic Thanks for the information. But will these issue types work like EPIC? Having Epic name and child issues?

Hi @Ramesh Krishnan Thanks for the question. I found the following article where it describes how you can do that. https://community.developer.atlassian.com/t/programmatically-test-if-an-issue-is-archived/35276

Dear @Line Veronika Nielsen You are very welcome.