Walter Buggenhout Community Champion

Hi @Evalaji Jones, If you know the end date of your sprint and the columns that are mapped to the rightmost column of your scrum board, that is not so hard to do. Suppose your sprint is called Sprint Koala, the sprint was completed on December 23rd, 2022 and the rightmost column of your board is mapped to the Done status,…

Hi @Savita Fulmali and welcome to the Community! These warnings are obviously there for a reason. You do not need to fix everything you see, but these warnings are there because it is known that certain things may make your migration fail. It is always better to prevent these things from happening rather than having to…

Hi @Jordan Trinklein, Yes. Just put "IN CR" between quotes, as the name of your status contains a space. 

Hi @Aysha Ahmad and welcome to the Community! JQL filtering does allow history searches on status, but it depends very much on how you built reopening an issue in your workflow. It is possible to perform a search like this: Status = Done AND Status was Reopened This search would return all issues that are now in…

Hi @Jordan Trinklein, This automation rule is the one you're looking for. All you need to do, is update the statuses to match your use case: Hope this helps!

Hi @Jordan Trinklein, First check if this project you are talking about is team managed or company managed (that should be visible in the bottom left corner when you're looking at e.g a board in your project). If it is team-managed, then be aware that this type of project does not share issue types with other projects.…

Hi @Axel Ulises Vite Navarrete and welcome to the Community! Could you elaborate what problem you are experiencing? This is a screenshot from a perfectly installed app 🧐

Hi @Sarah Fajerberg and welcome to the Community! Even though I am very much interested in agile ways of working, I'll stick to the technical part 😅 An issue is considered completed when it moves to the rightmost column of your scrum board. The only way you can make these issues appear in the next sprint, would be by…

That is what I was thinking indeed. So: get rid of the -> All transitions and redesign your workflow somewhat like this: You won't need any conditions anymore, except (if you want to be really exact) on the transition to Cancelled. It would make sense there to restrict that transition by applying Status Category != Done.

I am sorry, @Matus K, but you have lost me there. I am getting the impression that you are trying to use conditions on global transitions (those are transitions from a black All lozenge to a status) to disable certain transitions you don't need. If that assumption is correct, why don't you simply replace the transitions…

Hi @Lilia Gyurova and welcome to the Community! First of all you should create a filter to retrieve all the issues for your team. How you should do that, depends on how your issues are organised for your team. Suppose all (open) issues are in a single Jira project, then this is a good example: Project = "Your team's…

Thx @Marie Laplise! Glad it does and best wishes to you too! Since my tips helped, could you accept the answer below? That makes it easier to retrieve for other people with similar challenges! 🤗

Hi @Bar Abergel, Yes, the following automation rule could do the trick: The rule is triggered when an issue is created. An SLA has different states (running(), paused() or completed()). That's what I used in the condition at the second step: if the issue is created outside the calendar hours, the SLA state will…

Hi @Qasim Sajjad Zaidi and welcome to the Community! Great to see that you want to help improve the product by sharing feedback! In cases like this, you can reach out to Atlassian support to share your feedback. From within Jira, click on the ? icon near the top right corner and either select: * Contact support to raise a…

Hi @trubasa and welcome to the Atlassian Community! You may find answers to your quest in this article on Atlassian Developer and in related links on the left hand navigation. In addition, a good source to ask specific questions about app development and related topics may be the Atlassian Developer Community. Hope this…

Hi @Benedict Tarronas and welcome to the Community! Unless you are doing some very strange things, there is no restriction whatsoever you would need to apply. A transition simply changes the status of an issue; it does not automagically moves an issue into a different project. I would honestly not know how you would even…

HI @shivakumar B M, If these stories have estimates, then you will see your burdown line suddenly increase on the date you added the stories. This is considered and displayed as scope change on the chart. Hope this helps! 

Hmm; after testing it I must say I am a bit puzzled as well. I did not succeed in making this work with status category = To Do. I am wondering if that may be a bug. Anyway, the following workaround did work successfully in a test environment:

Hi @Matus K, I think the following should work: Hope this helps! 

Hi @jeroen_wilmes, Yes, that is possible. You can either use a different field configuration in different projects or - as an alternative - use different workflows with specific required field validation in your different projects. Hope this helps!

Hi @Silvana Heckelsmüller and welcome to the Community! First of all you'll need a filter that retrieves all your issues. To do so, navigate to Filters > Advanced issue search. In advanced mode (JQL) enter the following: Assignee = currentUser() AND Resolution != Unresolved This will retrieve all open issues assigned to…

You can even use the same SLA to automatically close the ticket when the SLA target of 40 hours is reached:

Hi @Marie Laplise, No worries about the French 😉 I believe it would be easier for your use case to use the SLA's to set up what you are trying to do. I think you are describing a classical use case where an issue enters status Pending (and thus requires an answer from the customer) and you want to close an issue…

Hi @Marie Laplise, We cannot see the exact data nor your automation rule, but most likely the problem is in your "update is equal to 1 minutes ago" part. Jira uses milliseconds for time based calculations and I would suspect that the time of change will not be exactly one minute ago. To make sure your automation works, I…

Hi @Maeneth, A JQL filter simply fetches a list of issues, based on criteria. So will the following JQL list all issues in Project A: Project = "Project A" All the attributes (request type, status, organization, ...) will be returned with every issue. If you want to display these attributes in gadgets on a dashboard, you…

Hi @Zia Ansari and welcome to the Community! I am sorry, but I do not really understand your requirement here. From reading your question, it seems as if every issue that gets assigned should automatically get a value of 40 hours? For every single issue in every project in Jira? Could you be more specific as to what you…

Hi @Victor Parera, I do not have an immediate answer to what you are trying to achieve, but rather a question to challenge you a bit on your requirements. Discovery basically discovers the items on your network based on how they are called. If you are going to introduce a naming convention that alters the names you…

Hi @Neil Green, Your observation that all time spent is returned is correct. That is because JQL (Jira Query Language) always returns issues. It does not return hours spent on those issues or anything else, just a list of issues. If you want to do reporting on time spent during a certain period of time, your best bet would…

Hi @Katharina Köpp-Wüst and welcome to the Community! Jira does not natively support this, unfortunately. The Atlassian Marketplace however may offer solutions that let you bulk clone issues to get you started when you want to fill up a project with your standard set of issues. Hope this helps!

Hi @Manuel.MAULINE and welcome to the Community! In Jira Service Management (JSM) there are calendars available to configure SLA's. Jira Software does not have this functionality, but you should be able to work around the issue, simply by letting your developers track their time. Out of the box, you can enter time based…