Walter Buggenhout Community Champion

Hi @Knirke Jensen, Go to the board configuration of the project your timeline belongs to and right there, enable the Include Child level Issues toggle. That should make scheduling for child issues possible. Note that they must have a parent epic for them to show up on the timeline as well ... Hope this helps!

Ok ☺️ - I see where you are confused. Any status in Jira has a name, but also a status category. That is what Da fare (to do), In corso (In Progress) and Completato (Done) represent. Usually, when people want to add a new status to a workflow, that will be an in progress status. When you click on Add In Progress status, a…

Hi @Sandhya Dilip Biradar and welcome to the Community! Licensing for market place apps is based on the number of users in your Jira instance. It does not have limitations based on the number of projects you have, nor additional costs for using it with an increasing number of projects. Licensing costs only increase as you…

There is no reason why you shouldn't be able to add a status with any status name you want, given you have the right permissions to do so and if you are doing so in the right place. Can you share a screenshot and a bit more context on what you are trying to do exactly and where you are in the product?

Hi @tim.leung.kt and welcome to the Community! I would recommend having a good look at your Jira custom fields and make sure there is only one Job End Date field in there. The one that's in your plan has ID 10237; in Jira it's possible to create multiple custom fields with the same name, so if you're looking at the wrong…

Hi @Andrea, You can add statuses in Team Managed projects as well. See This support article for more details on how to do this. It is good to know that statuses in a team managed project belong to that project only. So you can't add a status from the centrally managed statuses you use for company managed projects. Hope…

Great to hear! The {{issue.customfield_10115}} is a smart value, which is used in Automation rules to perform all kinds of dynamic actions. It does not work in default values for fields. To achieve your desired result, I would set up an automation rule in your JSM project that consists of the following steps: * Trigger:…

I have a test instance with a premium plan where I just tried how far I could go into the future and stopped scrolling in 2134, as I thought that would be largely sufficient: I cannot give you a decisive answer on how the basic timeline will behave in the near future, but I reckon that it does behave dynamically. So yes, I…

Hi @Ronald Lam, The issue title is the Summary field of that issue. If you want to edit that title, just open the issue, click on the title and change it any way you want. It is possible that this issue title is being set automatically (that would be the case if all issues raised from the portal are being created with that…

Hi @Ryotaro　kurusu and welcome to the Community! The basic timeline in Jira projects cannot be extended beyond 2026. In the premium plan of Jira, Plans (formerly known as at Advanced Roadmaps) does offer timelines that extend well beyond that date and can visualise your plan across multiple years. The Atlassian Marketplace…

Hi @Chris and welcome to the Community! Issues and List are 2 different views with similar functionality, but they are not the same: If all is well, both views should be available in your project. Hope this helps!

Glad to hear, @Jose_ Nimisha! Do consider accepting my answer, as that makes it easier to find for users with a similar question ☺️ 

Hi @Prasanna Kumar Kola and welcome to the Community! If you are trying to retrieve the child issues of a specific Epic (and you know its key, like you describe), you can query for them natively like this: parent = NS30319-17425 It is worth noting that this type of native filtering is not dynamic, i.e. you need to…

Hi @Jose_ Nimisha and welcome to the Community! In general, for questions about automation rules it is useful if you could share screenshots of your full automation rule, as that makes it easier to understand how far you already got in the process. For this scenario, if you add the labels field in the edit issue action of…

Hi @Geevarghese Jojo Joy and welcome to the Community! You can find a reference agreement right here and the procedures to sign one in this support article. Hope this helps! 

Hi @Raja Sekar and welcome to the Community! Goals are part of the Platform Experiences, which is currently available in early access. While so, permissions are currently not configurable, but are planned to be integrated at a later stage, as you can see in this extract from the early access program documentation: Hope…

I was more or less assuming that that was your approach. It won't work that way, unfortunately. If you add issues to a sprint, they will be planned with start and end dates matching the start and end dates of that sprint. That is not possible if your issues are too large to fit in a single sprint, which is - almost by…

Hi @Alex Wills, If you can limit the scope of your Lookup Issues function (the second step in your automation rule) to only the issues delivered by the team you want to report on, that should work. That does imply the team must be filled out on the issues in the sprint or you should find a way to filter e.g. the issues…

Hi @Jonathan Lewis, Your screenshot does not appear currently, but apart from that I am not sure what you seem to be struggling with; Your automation rule does process each ticket separately. But if your JQL filter returns multiple issues, it will process all these issues - one by one. Your JQL query is currently missing…

Hi @BLNSS and welcome to the Community! The only record I could currently find in Jira's public backlog is this feature request: JRACLOUD-84466. It is not much, but alongside the context that was already in the thread you referred to in your question, I hope it helps!

Hi @Preem, Atlassian is pretty transparent about its policies when it comes to Atlassian Intelligence and security. You can find a lot of resources to read up on in the AI section of Atlassian's trust center. Through Atlassian Intelligence and Rovo, Atlassian has been integrating quite some AI features in the products for…

Hi @Johannes Nyberg, In a scrum board in Jira, you normally can't schedule Epics in a sprint. They live in the Epics panel in the backlog where they help you filter the Epics' child issues for sprint planning, but in reality it is those child issues that are planned in sprints instead. The sprint allocation that you can…

Hi @Nikhil Kulkarni, I scheduled a call - quite short notice, I'm aware, but the scheduler allowed me to - to find myself alone in there. I have pretty similar questions I would like to discuss as @Alfonso Leiva's.

Hi @cuong_nt1, You can add marketplace apps to your sandbox and use them for free, as described in this support article. What I assume you are referring to, is that your app (and app data) gets lost when you copy data from production. That is true, as you can verify in this support article (see the list of data that can't…

Membership of an organisation is part of but does not define access to products, not projects in your site. If you navigate to Products in your site's admin console and click on Manage Product next to Jira Service Management, you should see a list of groups that is granting their members a certain role. There may be users…

I think that - as @Marc -Devoteam- explained, your confusion may be with the terminology of the "Organization" mainly. When someone creates an environment with Atlassian products in it, this also creates an (Atlassian Organization), which is the body that holds all Atlassian products (and users) in there. And so, when you…

Hi @Antonio E and welcome to the Community! I am making assumptions here, but I have the impression that you are mixing up 2 different organization concepts here. The one in your first screenshot is about the administration of your Atlassian site and all its products (like Jira, Jira Service Management, Confluence), while…

Hi @Linh Nguyen and welcome to the Community! You can edit the forms (and other settings) of projects after you create them. It is just worth mentioning that any changes you make apply to the project itself, not the template you originally created it from. That template is not editable for you as a user. That means that if…

Hi @Charlotte André and welcome to the Community! If you are an admin, navigate to admin.atlassian.com and check the Products page for your site. Which plan you are on is listed there. If you are not, you can check 2 simple things to verify if you're not on a free or premium plan. If you click Plans from the menu and see…

Hi @yosi hatem, If this is a screenshot from a company managed project, a sub-bug would be a different type of subtask. So, in that case, the feature is already there (it's just a matter of knowing that you need to click that one). If this is a team managed project, then this won't be possible as you can't add other types…