Walter Buggenhout Community Champion

Hi @Sanna Mäntynenä and welcome to the Community! There is nothing that you must do in Jira, honestly. Jira is meant to support the way you manage work inside your team and not dictate how your teams should bend the way they work to align with the tool. Having said that, start with a clear understanding of what you need to…

Hi @Lessandra da Silva e Silva _ Info Store, As an organization administrator, you should be able to navigate to admin.atlassian.com, on the products tab of the admin console find the option Manage subscriptions. Right there, you should be able to find the app. Click the ... button and select Delete to remove the product.…

Hi @andrewsharapoff, Advanced Roadmaps looks at the remaining estimate to track progress and is not aware of the value in the original estimate field. While usually the original estimate is copied over nicely into the remaining estimate field initially, I don't see any remaining estimate value in your screenshot. It does…

Hi @Evo Mind , Adding to the earlier posts of @Bastien Delourmel _FMX_ and @Michel Neeser, in order to be able to assign a user to an issue in your project, that user must have the right access to your project. Make sure that this user is assigned to a role in your project that has the assignable user permission (if your…

Hi @CC, I assume by higher levels in the plan you mean epics and issues further up in the hierarchy? If so, you may be better off clearing your start end end dates from those issues and have the dates roll up automatically in Advanced Roadmaps. In that case, they won't be saved tot the actual issues in Jira, but you can…

Hi @Armand and welcome to the Community! Your information is not gone; it is just hidden from the board after weeks because the board view is designed to help your team manage their work that still needs to be done or is in progress. Having a long list of items there that does not need any more work, makes it difficult for…

Hi @Lorenzo Lonati and welcome to the community! Yes, you should be able to add fields to a an issue type (as it is called) in Work Management. How it's done depends on the type of project you are in: team managed or company managed. Check out this support article for more details. Hope this helps!

Hi @Valentin Dachtler and welcome to the Community! Why don't you just export the data from the existing team managed projects to csv? That way, you'll have the actual data you are going to move for real to test with. In your team managed project, make sure the issue navigator feature is enabled. Navigate to issues from…

Here in the Community we won't be able to tell you. Many of us, like myself are volunteering to help people solve challenges and share knowledge; but we can't access your environment. As I mentioned, raise a ticket with Atlassian support for this. They can access your environment and tell you what is wrong.

Hi @Shivangi, That seems like a pretty clear explanation of why you can't access your board. If you are the admin for your site, update your billing details as indicated or reach out to Atlassian support and raise a request for Billing, payments and pricing if you think something is wrong. You can do so…

Hi @Taha Bakhach and welcome to the Community! That the parent link field is locked, means you cannot edit its configuration settings. But that should not prevent you from adding it to the epic screen(s). In your project settings, have a look under screens to find out which screen is used for epics. Either edit the…

Hi @Tharunkumar and welcome to the Community! For that purpose, create and save a filter that pulls a list of these tickets and then create a filter subscription for it that you can schedule to be sent out at a specified time. e.g. for the tickets created and updated during the current day, you could use the following JQL:…

Hi @bartlomiej.jochym and welcome to the Community! No, not in the standard plan of Jira Software or without marketplace apps. Out of the box, Jira Software has an issue hierarchy that looks like this: Epic -> Standard Issue Types (bug, task, story, ...) -> Sub-task You can't create an Epic as a child issue to another…

Hi @Kanishka Karunanayake, This may lead to a philosophical discussion somehow, but as a rule of thumb, try not to delete issues at all. They have been created for some reason in the first place. From what you describe, it almost seems as if you are trying to use your plan as a tool to review ideas and then only want to…

Hi @Dd , I am not aware of a way to update the default assignees for all your components. However, if I understand correctly, all your components are in a single project and it seems created issues are assigned to the component lead. You can set your issues to unassigned by default by going to project settings > details…

Hi @Admin OKZT , When you add columns for a specific filter, make sure that you have selected the filter tab in the list with available columns before you make any updates. If you have accidentally selected any of the other tabs, you are updating default settings instead of the filter. On the other end of the story, when…

Hi @Jordan Trinklein and welcome to the Community! If I understand your use case correctly, try the following: (issuetype in standardIssueTypes() AND statusCategory != done) OR (issuetype in subTaskIssueTypes()) Hope this helps!

As I tried to explain, the default status an issue gets is the initial status in your workflow. If you look at that workflow, you will see a sort of grey circle indicating the start of the workflow and a line going from that circle towards to do. If you want a different initial status (before or instead of to do), you'll…

Hi @Tata Tatkhashvili, While I am not 100% sure if I understand correctly what you are trying to do - issues in Jira always have a status. That status is determined by the issue type's workflow and is normally the first status in the workflow. If you want another (initial) status than to do, what you would normally do…

For issues to be considered complete in this board, yes - that is the column they should be in.

Hi @Andrew and welcome to the Community! Jira considers issues in a sprint to be open as long as they are not in the rightmost column of your board. That is most likely what is happening here. Status or resolution don't matter here, just have a look where the issues are on the board and have a look in your board settings…

Hi @Kate Turcotte and welcome to the Community! All you need for this, is a filter that pulls in the data that had a status change to the deployed status on the previous day. As JQL supports history search on status changes, you should be able to use the following: Project = "<Your project>" AND status CHANGED TO Deployed…

Hi @Sadagopan, Sarangapani and welcome to the Community! While I still am not entirely sure what timeline you are referring to in Jira, your dates should be stored on the Jira issues themselves. Have you tried using a Jira macro in Confluence where you pull in the issues you have on your timeline, display the the macro as…

Hi @Mélanie Liguet, I have not tried going so far in restricting permissions personally using workflow properties to be honest, but you may be running into this issue that is mentioned in workflow properties documentation : I am not sure where in your workflow you are trying to apply these restrictions. A common scenario…

Hi @STX, Atlassian indeed strongly believes in open work (Research on the benefits of open work) and openness is therefor a default starting point. When organizations start using Atlassian tools, it is usually not the case that there are suddenly dozens or hundreds of projects, spaces or service desks created and live in…

Hi @Anth.Burnikell and welcome to the Community! Sorry to start with a question - but I can't quite imagine why you would want to do that. Everywhere in Jira, when you search for or view and issue, the issue key is displayed by default alongside the summary (in a board, on dashboard gadgets, in quick search, ...). It…

Hi @STX and welcome to the Community! Check the permission scheme attached to your project, first of all via project settings / permissions. Make sure that browse project / assignable user / ... is not set to any logged in user, as that would effectively make your project accessible to anyone with a Jira license,…

Hi @Appam Aparna , You can't set components by default in the creation screen; You can use automation to set them automatically after an issue is created. That is not like a default in the way you describe it, but it lets you set one or more components when your issue is created. Hope this helps!

Hi @fg and welcome to the Community! That is currently not possible. Jira's standard issue hierarchy is Epic > Story (or other standard issue types) > sub-task. On a premium plan, you can add additional levels above epic, but you can't insert issue types in between epics and other issue types. Atlassian is currently…

Hi @Waseem and welcome to the Community! I am not sure which app you are referring to, but you can definitely add marketplace apps to a free plan. Just check out the pricing tab on the app's marketplace listing to validate if the app is free or comes at a cost to avoid surprises in that area. Hope this helps!