Walter Buggenhout Community Champion

A bit of a mix of @Marc -Devoteam- and @Robert DaSilva with a tweak of your smart values should do the trick: Hope this helps!

Hi @Veronika Hájková and welcome to the Community! For issues with billing and invoicing, reach out to Atlassian support directly via https://support.atlassian.com/contact/#/ and raise a request in the billing, payments and pricing category. In the Community here, most of us are Atlassian users like yourself who can't…

Hi @Jedsada R_, Incorporating JSM into your own solution is most likely not allowed by Atlassian's license agreement, that your can review here. See specifically paragraph 3.2, where it says: 3.2. Restrictions. Except as otherwise expressly permitted in this Agreement, you will not: ... (b) rent, lease, distribute, sell,…

Hi @JOSE ALBERTO RIVAS VARGAS and welcome to the Community! You have posted your message on a platform that is very much dedicated to helping users of Atlassian tools like Jira, Confluence, Bitbucket, Trello, Loom and more. Whatever platform it is you can't get access to, you will probably find the best and fastest support…

Hi @Hila Federovsky and welcome to the Community! Since Email This Issue is a marketplace app (by MetaINF), you might get faster / accurate support for this issue by reaching out the app vendor directly. You can find their contact details on the vendor's marketplace listing page. Hope this helps! 

Hi @[deleted], Have you read through the SLA documentation on how this works? To give you a very short introduction: SLA's are a feature of Jira Service Management. They use a (team) calendar to take into account what the working hours are of your support team. You can create one or multiple SLA goals in your service…

Those are not extra sub-tasks, @Andile Luvuno. They are the same sub-tasks as in your second screenshot (you can see that by their issue key). The last screenshot is a view from - what I think to derive from the visible part of your screen - a JSM queue. That is just a view that just lists all your issues, but is not…

Hi @Jobson Martins and welcome to the Community! Are you referring to a box somewhat like this: If so, this is a smart link. It has nothing to do with standard or premium - my example is coming from a free site. It is also not a very new feature, but something that does exist on cloud and not on Data Center, e.g. While…

Hi @Andile Luvuno, sub-tasks can't be created without a parent, so you honestly got me confused there about this statement: when the rule ran, it created the Sub-Tasks inside Each created Task and then proceeds to create the same Sub-Tasks Outside as New "Sub-Tasks" Can you share (a) screenshot(s) of your full automation…

Hi @Andile Luvuno, For a scenario like this, I would assume your sub-tasks are fixed / default sub-tasks. Quite simply, set up your automation rule like this: The condition I added in the second step is a way to control that subtasks only get created when my created issue meets certain criteria (in my example, if it has…

Hi @Frank Möller and welcome to the Community! Looks as if something is broken there. I would first of all do what the message says: refresh, wait some time to see its a temporary glitch that recovers itself, clear your browser cookies. If you are indeed on a free plan - as you tagged your question - you are not entitled…

Hi @Traci_Burke and welcome to the Community! Before you start to put too much focus on bombarding people with emails, I would recommend you to consider thoroughly if you really want that ... If you are bringing your team's work into Jira and onto a board, the created issues will automatically appear there once they are…

Hi @Carla and welcome to the Community! Sad to hear this happened and great that you have collected all this information, but the community here is largely populated by fellow users who try to help out where we can. We cannot access your site or apply technical fixes there. Reach out directly to atlassian support and raise…

Valid point and - apart from the shout out to vote for the bug - decent best practice advice, @jeroen_wilmes. Adding sub-tasks to issues ranked higher in the issue type hierarchy will cause complications in many places. 

Hi @Lavinia.Popescu and welcome to the Community! No, that's the way a labels field is designed to work: it is the perfect combination of (semi)structured data that allows users to add options that are not in the list (without the need to have administrator permissions). For the use case you describe, it is probably a more…

Hi @Vara Prasad, You'll have to provide quite a bit of additional information to allow us to help you. Are you using Jira Cloud or Data Center? If it's Jira Cloud, what project type are you trying to create stories in: is it company managed or team managed? How are you trying to create these stories? Is it from within an…

Hi @Dariia Strelnikova and welcome to the Community! Great that you're interested in connecting with other Atlassian customers and enthusiasts. You may want to read up on what your Community journey could look like in this Community Article. I would also recommend that you familiarise yourself with Community guidelines and…

Hi @Alena Bogomaz and welcome to the Community! That is an ask vanilla Jira (out of the box) is not really equipped for to answer. It does have a built-in field called Work Ratio that nicely calculates the comparison between original estimate as a percentage, but this remains at the issue level and does not take into…

Hi @jeroen_wilmes, I'm afraid that's a pretty tough ask, since @mentions to other people are pretty unstructured and free-form data that can be in all kinds of fields in Jira. Anyone in your organisation can be mentioned, in any text field on issues and by anyone else in your organisation. Since there is no link to who…

Hi @Rabab Rizvi and welcome to the Community! I wish I could tell you otherwise, but afaik these pages are fixed and not configurable. The What / Why / When successful are key components of the Atlassian Loop framework that is behind the tool. Hope this clarifies!

Hi @mattics phi, Assuming that you know the issue keys of the epics you would like to exclude, the following approach should work: issueFunction in issuesInEpics("'TextField1' is not EMPTY AND Key NOT IN (ABC-1,ABC-2,ABC-5)") In my example, ABC-1, ABC-2 and ABC-5 are the issue keys of 3 epics I would like to exclude. Hope…

Hi @david_napoli and welcome to the Community! There may be quite a few reasons why your rule may not function correctly. But the most likely reason is that the linked issues in your different projects may not be sharing the same workflow. And in that case, copy the target status from your trigger issue is more likely to…

Hi @James Cha and welcome to the Community! I am not sure if I understand your question entirely. But if my assumption that you are trying to apply a specific issue hierarchy in a single plan (a different hierarchy than in other plans), I am afraid I will have to disappoint you. The issue hierarchy is configured centrally…

Hi @Sadaf Oakasa and welcome to the Community! When you add a new field to a project (and to the screens used by the issue types in that project), you will be able to use that field on both new and existing issues in your project. However, if you want to add data to the field (also for old issues), you will need to update…

Hi @Gustavo Ezequiel Szemruck, That's not possible. Organizations are only available in JSM to share requests with their members on the portal. They don't have a function when it comes to granting permissions. You'll need to use user groups to set up the desired behaviour. While there are long standing requests for this…

If you can't add both groups into one property, add the property twice (for each group). 

Hi @Vincent van den broek and welcome to the Community! Tickets don't "land in a queue" - they land in your service project and a queue is nothing more than a filtered list that displays tickets that match certain criteria. But - having said that - that means that you can indeed create a queue that displays tickets…

Hi @Muhammad Tahir and welcome to the Community! Have you tried without the .include to specify your property. That is not supposed to be there: jira.permission.attachdeleteall.group For more details and examples, see also this support article. Hope this helps!

Hi @Emilia KASPRZYK, You can set up a JQL condition for this. It would allow you to specify your condition exactly the way you mentioned in your question: add a filter with the following syntax: StatusCategory != Done Hope this helps!

Okay, @Edgar Pusklevic, Since I can see you're struggling, here's a sample to get you started: But do spend some time and effort to read through the automation documentation and experiment. We're users just like you who are happy to help you overcome problems and struggles, but not a free work force to do the work for you…