Walter Buggenhout Community Champion

Hi @shivakumar B M, Yes, but only if you set the estimation statistic of your board to Remaining estimate and time spent (in Board Settings > Estimation) When you use story points / issue count an issue is only considered done when it reaches the rightmost column of your board. In these cases, there is no partial burndown…

Hi @Irem Odemis, Your first project is team managed whereas the other one(s) are company managed. These types of projects have a different configuration and serve different goals. Basically: team managed projects are designed for use in and by a single team, with no need for collaboration or sharing with any other teams.…

Hi @Sarim Bajwa and welcome to the Community! It seems the app is only available for the server version of Jira. There does not seem to be a version for cloud available. Which is why you cannot install it on your cloud instance (server and cloud are technologically different platforms). If you want to know more about the…

Well; it is essential that you do have request types configured for the issue type you are trying to create. If you're unsure if this is all properly set up, check Atlassian documentation to learn more. As an alternative, instead of doing complex manipulations to get the csv import right, you could also consider setting up…

Hi @Gala Vercellino, If your Jira instance is a free plan, that would be surprising since permissions are not configurable there. On the other hand, you indicated that you are on a standard plan. In that case, you should be able to access the project settings, as long as you have admin permissions. Click on the cog while…

Hi @Jurica Petricevic, Yes. As a Jira Administrator navigate to your custom field's configuration and select User filtering there. Check the box Enable group or project role filtering and select the desired group(s)/project role(s) from the list. Hope this helps! 

Hi @ori gal, Losing data from custom fields in a migration from team managed to company managed projects is - unfortunately - expected behaviour. This support article explains what may be lost during a migration. There's a couple of scenarios you can use to recreate the data, as long as you take the necessary precautions…

Hi @Wesley Payne This change in capacity management was announced quite some time ago (in early 2021). While planning capacity at the individual level allows for great detail and accuracy, it also entails a lot of planning overhead. The individual planning features were part of Live Plans, which are also being discontinued…

Hi @Mohamed Saad Taha, Request types in JSM use some weird and complex keys rather than the description you see in the UI. This related thread explains more about how it works and how you may be able to retrieve them. Hope this helps!

Hi @[deleted], I am not sure if I understand your question correctly, but Tempo Timesheets is built for tracking time spent, not for estimating issues. Your estimates go in the original estimate field in Jira. Having said that, when you log hours using Tempo Timesheets, the hours you enter go into Jira's Time Spent field…

Hi @Roger Kessler and welcome to the Community! The thread you refer to is a pretty good one in terms of context and approach. Project permissions in Jira are pretty granular. Create issues is a different permission than browse project (view the project) and edit issues. If you add a custom field to add users to issues…

Thx for that additional input, @Eran Roiter. Not obvious, but found it: you can unselect the default value selected on the configuration page by holding CTRL (on Windows) or COMMAND (on Mac) when you click it once more. Then save and you're back to a blank default custom field.

What type of project is this? Company managed or Team Managed? And what type of custom field?

Hi @Victor van Overbeek and welcome to the Community? It depends what is in your template. From what you describe, it seems that your template may be a Jira project, but that is not really clear from your description. If it is, you can create additional Jira projects using the initial one as a template. At least, if you…

Hi @Eran Roiter, You might have set the field as required in your field configuration scheme? That would make the None option unavailable that you would normally set to leave a field blank by default. 

Hi @[deleted], Is this a blocking message or just a warning? In the last case, if you are sure that you won't lose any data and the message is not blocking you from doing the move, just go ahead and transfer the issues. It may be just a generic, are you really really sure type of message. Hope this helps! 

That's a team managed project. Custom fields in that type of projects are restricted to that project only, which is most likely why they are not available in your automation rule. As a workaround, you may want to try using a smart value instead, though I'm not sure of the outcome with your project type either. Instead of…

Hi @Mohammad Munirud Doja, Can you check / confirm that these other fields are single user custom fields? If they aren't that's most likely why they do not appear and why you won't be able to use them as such.

Hi @Tom De Coninck and welcome to the Community! You cannot restrict access to a subset of articles from the knowledge base to JSM organisations. The way knowledge base articles are displayed is pretty open, as you may have learnt from your initial setup experience. If you want separate content for your customers, that…

Hi @Bluebinaries-DigitalMobility and welcome to the Community! Could you be more specific in what you are trying to achieve? * Where are you trying to create your filter? As a quick filter on a board? In the issue navigator? ...? * Can you share the filter you created? * Can you explain in more detail what the expected…

Hi @Mohammad Munirud Doja, You can simply copy the value from one field to another like this: I don't have a QA field in my test instance, so used responsible instead. But the idea is exactly the same. With the edit issue action, select the Assignee field as the field you would like to update. With the ... button next to…

You are referring to your entire board as the backlog screen, so it seems, @Nico. While the backlog is basically the items that are waiting to be started. The columns on your board represent the different stages your work goes through and done is one of does stages: the final one. It may be useful to have your completed…

Hi @Yakov Melman, Have a look at this related question, where Bill shares the smart values you can use in automation to set the right values: {{sprint.endDate}} Hope this helps!

Allright! If it works, do take a second to accept the answer. It helps users with similar questions to find help more easily!

Hi @Maeneth, I am not sure if I understand your question correctly. Just assuming that you want to update the status of a JSM ticket when a linked issue (e.g. a related bug) in a JSW project is updated, you can use automation to do that. This sample rule from the template library shows how you can use the transition of an…

Hi @Barış Özer, No, obviously not. The email will be sent after 47 hours and 59 minutes. I have the impression that you still don't see how it works 😅. Your SLA target is 48 hours. That is what you have set in the SLA configuration (your first screenshot). Everything you do in your automation rule trigger is relative to…

Hi @Guadalupe García and welcome to the Community! No, SLA's can be configured using JQL filters. Which means anything you can search for can be used as a basis for your SLA setup. In this example, priorities are being used: If you want to set up SLA's for services, my key recommendation would be to design the requirements…

Hi @Barış Özer, Your SLA configuration seems correct. So does your first automation rule that sends the email. But the second automation rule that updates the issue status to resolved should simply have the first option breached selected. 

Hi @Noam Castel and welcome to the Community! I have seen this behaviour before and - if I remember it well - this is because somewhere on the timeline (probably in the past), there is a number of parallel sprints in your plan (I mean starting and ending within the same date range). These sprints are then displayed below…

Hi @Jatin Bansal, Based on what you describe, it seems that your issue types are using a different workflow. It also seems that these different workflows have different validators in place. I would recommend you to check your Project Settings > Workflows and see what workflow each issue type is using. Then, open each…