Walter Buggenhout Community Champion

Sorry, I noticed you are talking about status category. While it is very likely that status category is not supported for history search, you can easily list the statuses in that category: Status changed to (Closed, Done) DURING ("2024-01-01", "2024-01-31")

Hi @Rahul, The following JQL should return those issues: Status changed to Done DURING ("2024-01-01", "2024-01-31") Hope this helps!

Hi @011_avinash, A lot of Jira configuration is based on issue types: the screens, the workflow, the field configuration. If you change an issue's type, you are at the same time (potentially) moving it to a different workflow, might loose custom field information as a consequence. As that needs to happen in a controlled…

Hi @jakubpietrzykowski and welcome to the Community! The whole release hub has been undergoing major changes over the last year or so. You can read more about those in this Community article, where you'll also see that the approvers feature was not there yet at the time of writing. Today, it is present on screen, but more…

Hi @Brayden Guill and welcome to the Community! No, the focus of Plans is different. Rather than focusing on the presence of your individual team members, it lets you specify the number of days / story points your team (rather than individuals) can deliver in a certain timeframe. Estimating your issues then helps to…

Ok @BenWade, ok - that clarifies the issue a bit more. A couple of things in that case. Let me start with Epics, as they have a specific behaviour. * If this is a scrum board (and you are using sprints, which I cannot see from your screenshots) - Epics are displayed in a separate panel that you can enable/disable from…

I have checked the screenshots, @BenWade. I am not sure what I can add: to that. You share screenshots from 2 different projects / boards. As I explained, projects can be configured to use different sets of issue types. And so there is nothing strange about seeing different sets of issue types in different projects. What…

Hi @BenWade That is perfectly logical. The board filter shows your board is getting issues from 1 single project. The issue types available in a project are defined in the issue type scheme linked to that project. In business language: you will only be able to create the types of issues available in the project you select…

Hi @Fabien Thoumsin and welcome to the Community! I am not familiar with the JiraPS module you are referring to. But I would expect you should be able to do this with automation, most likely not even through the advanced fields option you are trying to use. With the edit issue action I would expect you to be able to just…

No, in a company managed project, they don't @Mahesh Kumar CD. If they are assigned to a role that has administer project permission in that project, that is enough. To grant users product access (and at that point a Jira Software license), you need user admin rights at a higher level. That may be what you are referring…

Hi @[deleted] and welcome to the Community! I hope you don't mind me answering in English ... Your issues won't have disappeared. If you change the workflow, that usually means you add and remove statuses. And - most likely - the new statuses you added are not mapped to columns on your (scrum or kanban) board. So, on the…

Hi @Laura van _t Wout and welcome to the Community! I am just a bit unsure about one part related to your 1st question (will this work). The basics are there, but I am not sure if Sprint = {{Sprint.name}} will work. I haven't tested, to be honest, but I would not be surprised if you would rather need to use the sprint.Id…

Hi @shantanuw and welcome to the Community! There is something odd in your scenario. You say you want to update field values in subtasks, which leads me to assume this is about already existing sub-tasks in Jira. Your mention that this is something you would see as a regular, recurring process even strengthens that…

I was somehow expecting you would say that, @Steven Vits, When seeking assistance for automation rules, it is always difficult to fill in the blanks from only a description and no insight into the whole construction of the rule you are struggling with. It's always best to share your full configuration (though I understand…

Hi @Dave Noble, Atlas does not have an API available yet, as you can read in this related thread. So the endpoints you would need to automate status updates from other products are not available yet either. The post I refer to above also mentions the intention to take steps there in the (currently undefined) future and how…

Hi @Alejo and welcome to the Community, While I haven't done this myself, you connect Github to a project in Jira. Since your project must be migrated before you can connect anything to it, it seems logical that you migrate your data first and connect Github afterwards (otherwise, there is nothing to connect to). The…

Hi @Steven Vits, The easiest way to add actions to your most recently created issue would indeed be a setup like this: Hope this helps!

Hi @Anjana Shrivastava, I am sure you are aware that this is not a simple ask, that will not be solved by a template or one or two quick actions, right ... If you suddenly see spikes in the number of issues being reported for a product, you can quite confidently make an educated guess that something has changed. A big…

Hi @Clement Matiku (EXT - Smollan) and welcome to the Community! Could you give a bit more details about what you mean? Do you want to report a quality issue? Write a blog post? Get support from someone at your company? ... 

Hi @Arsalan Ayub and welcome to the Community! Have a look at this support article. In short, you can either import data from Bugzilla by first exporting them from Bugzilla to csv or by importing them into a DC instance of Jira first and then migrating them to cloud. Hope this helps! 

Hi @Sjoquist, Carl, I hadn't noticed that before, but trying this made me notice the same behaviour. It seems the drag and drop has been replaced by an option to select an epic right from the issue in the backlog by clicking the + Epic button you see there: Not sure why the drag and drop does no longer work, but I can…

Hi @Osama Al-Areky, Scriptrunner for Jira Data Center and Scriptrunner for Jira Cloud are different products with different feature sets. I guess the documentation you've seen is for Data Center - there are many more built-in scripts there indeed. Hope this helps! 

It isn't obvious, that's true. But you are doing some advanced stuff there, you know! 😛 Glad it worked!

Hi @Nicolai Viținschii and welcome to the Community! From the panel on the right in your last screenshot select Brach rule / related issues. Then, a dropdown will appear where you can scroll down to select For: issues in the sprint. That's what you need. Hope this helps!

Hi @Samuel Lugtu and welcome to the Community! Can you be specific about what reports you are downloading and the steps you follow to do so? And also what you mean by the customer ticket tracker. Happy to help, but you need to provide more details if you want us to say something useful 🤗.

Hi @Vignesh Jayagopal, Take a look at why you have set up different instances. If you want to give people access, they need a license or they won't be able to access your site. That's how it works. Very often, by managing permissions to your projects properly, you can let your teams work in the same site while making sure…

Yes, @Deniz Ocak. You can have one (instance of a) product in a site and multiple sites in an organization. Each product (in a site) can be any version you like. If your organization is Deniz, you can have 2 sites in there: Deniz1.atlassian.net and Deniz2.atlassian.net. In Deniz1 you can run Jira Software Premium, Jira…

I still don't quite get what you're trying to do, @Massimiliano Stretti. You can use the Lookup issues action in your automation, using JQL to get a list of linked issues. After doing that, you can use the {{lookupIssues}} smart value to add information to your description. Still, if you are going to that on every…

Hi @Massimiliano Stretti and welcome to the Community! That is a very strange requirement. The list of linked tasks is visible on your issue just below the description, under linked issues. Could you explain why you would want to repeat that information in your description field (of all places 😛)? Sorry for challenging…

Hi @Anders Hamborg Nielsen, Epic name is being deprecated. The field has been consolidated into the summary of Epic issues, as it was considered to be redundant information. While I am not sure if this is why it is no longer pulling data from Jira anymore, it is best not to use the field anymore. Just a long shot (and…