Walter Buggenhout Community Champion

Hi @Charlotte McPherson _US-ENG_, You should be able to find out where in your hierarchy features are configured in your instance. * Select Setting > Issues. * In the left column, go to Issue type hierarchy. If features are listed as an issue type there, you should also see what its parent is. If you don't see them, they…

Hi @kirsten.lynch and welcome to the Community! If my understanding is correct, Behavepro is a marketplace app on top of Jira. The best thing you can do, is reach out directly to the app vendor to discuss the issues you're facing with them. Hope this helps!

Hi @Cody Andres Alessio-Bunnell and welcome to the Community! The timeline view in JPD is not a Gantt chart and it does not have the ambition to become one. It is intended to create an overview of the (bigger) ideas on your product roadmap and to prepare those for delivery, but without including those details here. Once…

Hi @Colleen Gotling, I understand your point; unfortunately there is no time only custom field available in Jira - there is a feature request for something like it that you can track here: JSWCLOUD-15988. Forms are an acquisition Atlassian made a while ago; it used to be a Marketplace app called ProForma and is now…

Hi @Ayush Pathak, No, I am afraid not. Can you elaborate on the deeper goal you would be trying to achieve by doing something like that? Most likely, there's other / better ways to get to the desired result. Hope this helps!

Hi @Ramos, Miguel (Contractor) and welcome to the Community! Assuming you created a site by accident and you want to have it removed, see this support article for instructions. If you created the site yourself, you should have the necessary permissions to perform the steps described in the article. Hope this helps!

Hi @Shazia Khan and welcome to the Community! No. On a free plan, all users have full admin permissions and you cannot configure permissions. Hope this clarifies!

Hi @Kinze Ren and welcome to the Community! You don't add a status to an issue, but rather to a workflow. You can then use that status to the issues that are using that workflow. Where you add a status depends on the type of project you are in. You can usually see that on a board, near the bottom left corner of your…

Hi @Kovida-Yash, As you refer to Jira Service Management, when you create an SLA you can set conditions to start and stop the SLA timer, but also to pause them. Considering you have added your new status to the workflow used in your project, all you need to do is add that status to the pause counting time section in your…

Hi @Shayden Frankhouser and welcome to the Community! At the core, you basically need an automation rule that looks like this: Because you are working across 2 different projects, you may need to make sure to include both projects in the scope of your automation rule (you can do so on the Rule details page). And also pay…

Hi @Jason Finan, This error seems to suggest you either have a workflow validator in place that is checking if the Accessible custom field is filled out, or someone set the Accessible field as required in the Field Configuration Scheme behind your project. On top of that, the field is probably not listed on the create…

Hi @Irina Poghosyan, I am just guessing you are using company managed projects (for team managed, the field to use story points is called story point estimate). If so, story points are not available because the context of the story points custom field is limited to the story issue type (in my test instance, it is also…

Hi @Sissy Lynn and welcome to the Community! No, unfortunately not. If issues have really been deleted, they're gone. To prevent this from happening, if you're using company managed projects, you can revoke the delete issues permission for users of a project, an approach I strongly recommend. Team managed projects - alas -…

Hi @OM and welcome to the Community! You are right if you want to use an issue type to represent goals. But since recently, Atlassian offers an actual Goal concept. It came original from Atlas, which is now being incorporated into Jira / Atlassian Home by default. That should allow you to link (even multiple) issues to the…

Hi @BHANU TEJA, No, at least not in the same way. Time to first response and time to resolution are SLA's. They work with a timer, a calendar and targets, which you set from the SLA feature set that is specific to JSM. So, no, you cannot configure those in the same way in Jira, simply because SLA features are not available…

Hi @Chike Okafor and welcome to the Community! You would still need to link people (or groups) to that role to make sure that they get to browse the projects using that scheme. Linking people to a role is something you do project by project. Apart from that, what happens to projects with a different permission scheme,…

Hi @Gina Novoa and welcome to the Community! I don't quite like being the bearer of bad news, but deleting issues from Jira is quite destructive, I'm afraid. Unless you have a good backup solution in place, there is no recovery option anymore. Deeply sorry that I can't bring a happier message 🥹

Hi @Arun Singh and welcome to the Community! JQL - unfortunately - does not support searching by sprint start or end dates. There is a feature request for this that you can track here: JRACLOUD-72007 Hope this helps!

Hi @Sabrina Boetzkes, From your explanation, I cannot clearly derive what brings you to the statement that "it" still has an SLA. In short: if you specify a JQL filter to add target timings to your SLA, a box with that SLA target and a timer should be displayed on issues that match that filter. Issues that don't match the…

Hi @Ken Camarador and welcome to the Community! You could consider a couple of things, a first being more restrictive in your query. If you want to only select issues created more than 2 days ago, but less than 4, the following might work: created <= -2 days AND created >= -3 days You can then use similar criteria to deal…

Hi @egroot and welcome to the Community! You will need to locate the person responsible for managing your Jira Service Management instance internally, I'm afraid. When you have no more licenses available to add additional people to your project, there's 2 things you can do: * evaluate if there's any of your current users…

Hi @Nourhan Tarek and welcome to the Community! That would need more clarification, I'm afraid. When you say "download a report", what are the steps you follow. What report are you talking about? Do you see a value for resolved in Jira and not in the data export or is it something else? Apart from that, when you're looking…

Hi @jeroen_wilmes, Yes, that is very much how it is intended. In an attempt to clarify a bit further: Atlassian ships its products with a couple of out-of-the-box roles. At product level, these grant a user a license to use an Atlassian product and - optionally - some additional super powers. A user is licensed to use the…

Hi @m_borg and welcome to the Community! The navigation (even on a free plan) should look like this: If you don't see these options, can you verify you really are on a cloud version of Jira? If so, the url should end with ...atlassian.net. If so, you might need to get in touch with Atlassian support to make sure there's…

Hi @Steven DANTAS and welcome to the Community! Just based on your input, I would be tempted to say "Yes", this is normal. If you are using a free version of Jira, using the built-in timeline view with no marketplace apps installed, you don't have a resource planning tool in your hands. The timeline is a visual…

Hi @Claire Buffet and welcome to the Community! That is hard to tell with only that information. It is possible that certain fields are required when you are creating an issue in your project and that these fields are not filled out in your plan. Or there may be a permission issue with one of the projects. Or ... It might…

Hi @Cassandra Fitzgerald and welcome to the Community! You might consider using Releases to represent your PI's. They are an out if the box feature in Jira and they have a start and end date associated. You can find a bit more information through this support article. Hope this helps! 

Hi @Marta Mita, There is no information on that matter in the documentation. That suggests that there is nothing in place to remove the URL from the history and: * you may assume that it will stay there; * at the same time it would be wise to communicate with your users to use the new URL consequently and modify any…

Hi @Mélanie Liguet, No, JPD is under the hood based on team managed project architecture and that does not support issue level security. The idea of putting secret ideas in a roadmap intended to create visibility and collect insights around those on a larger scale goes a bit against the philosophy behind the product, I'm…

Hi @Sandeepsai, SLA's are part of Jira Service Management. You can read more about the topic from this collection of support articles. Hope this helps!