Walter Buggenhout Community Champion

Hi @abhishek_sharma03, Your sprints are a feature of the board they belong to. And the normal way of closing them, would be from that originating board. There is a helpful JQL function that can help you find all issues in active sprints across Jira: Sprint in OpenSprints() This will return all issues across all active…

It must be this one, @carlos_marin and @Jack Brickey : Jira Product Discovery Chrome extension 

Hi @carlos_marin , I am pretty sure that this is part of Jira Product Discovery. Hope this helps! 

Hi @mahya golbaz, Those are just system dates. They are fixed dates behind the scenes that indicate when an issue was created, last updated or resolved. Jira has the funny habit of displaying not the actual date, but an indicator in human language of how long ago this system event happened. Don't worry about it. It is not…

Hi @jeevan, First of all, have a look at this support article to get you started on the core principles of csv-import. You can read there how you should structure the file etc. It even has a specific section on importing sub-tasks. In the example given in that article, very long issue id's are being mentioned. I can…

Hi @Javanshir Mustafayev _ HIT, If you were on Jira Software Premium, advanced roadmaps would be able to roll up target dates of child issues to all levels above in the roadmap view. So that would be a graphical, out-of-the box option. If you don't, you could set up an automation rule like this one from the template…

Hi @pbland and welcome to the Community! That syntax is definitely not standard Jira - not even on the server platform. I am pretty sure that you used to have an integration app in place on your server instance to connect Jira and Salesforce. Most likely, you have one that connects you cloud instance to Salesforce now, but…

In a very short time I have become a big fan of Atlas. Of the product, but maybe even more of the work agreements and proces it embodies. One of the building blocks is the project directory, where you should answer 5 deceivingly simple questions about your project: * what is that you're actually doing * why are you doing…

Hi @Hardip Singh, Using bulk change is not going to help you to update sprint names. What it actually does, is updating the link between the issues and the sprint they are in. In other words: you would not be updating sprint names, but essentially assigning issues to different sprints. It does not make much sense to update…

Hi @Kristine Gemici, The sandbox is a feature of the premium and enterprise plans. Maybe your Jira Software plan is not one of those? If so, that is probably the reason. If your Jira Software IS a premium or enterprise plan, than I would recommend you to reach out directly to Atlassian support…

Hi @Aida Johnson and welcome to the Community! There seem to be a lot of ways to connect Jira with webflow through a lot of connector apps. A quick online search on Jira webflow integration will helo you surface plenty of options. At the same time, Jira Dashboards out of the box can be configured as a wallboard slide show…

Hi @Malavika L P, Trust you timesheet application for this. The problem with JQL (when speaking about time tracking) is that it retrieves issues, and not worklogs. While there is nothing wrong with your filter, it retrieves all issues that have worklogs during the given time frame. But it also returns all the time spent…

Hi @Bekah Dumaup and welcome to the Community! Updating your workflow does indeed update the status of all tickets using that workflow. Updating your workflow again would lead to the same result and update things yet again. Although I can imagine this is not really great when you look at past data, I would not spend too…

Hi @Paul Madison, No, there isn't really. Search is keyword based. The only thing that really impacts what request types show up, is permissions on your projects. A customer performing a search will only see request types appear from JSM projects he/she has access to. Hope this clarifies! 

Hi @Shilpa Sikotra Taylor, You should be able to do so by updating the estimation statistic of your board. You can select a different statistic through board settings > estimation. Hope this helps!

Hi @[deleted] and welcome to the Community! The feature you describe applies to a team managed project. If you are still managing a team managed project, then maybe you have different workflows for different issue types. In that case, as a workaround you could navigate to project settings > issue types > select an issue…

Hi @Gabriel Radic and welcome to the Community! Things don't work that way. An issue is in the backlog of your board because it is in the status that maps to the backlog (status) of your board. You should be able to derive whether an issue is in the backlog from (on your screenshot) the big blue status indication. If…

Hi @akinsanya.oluniyi and welcome to the Community! The assignee is the person who is currently the owner of the issue - he or she in charge of getting the work done. The assignee can change when you hand the issue over to someone else. The reporter is the person who reported/created the issue. This one usually does not…

Hi @Justin King, This is a great step forward and it is greatly appreciated. Not entirely sure what this means with regards to managing the actual data in Insight. Does it still require a JSM Premium license to add new objects?

I am not an API expert, @Vikas Sharma, but inactive users don't have the necessary permissions inside the application to log work. So I have my doubts if that would be possible. 

Hi @Lisa Besteni, As you can read in this support article on the Velocity chart, issues are considered done if they are mapped to the right-most column of your board. That is the only requirement. Hope this helps!

Hi @Vikas Sharma and welcome to the Community! Unfortunately, only actual users can log work in Jira. Or: work logs in Jira are always logged for an actual, existing user. There even is a permission associated with it. You could try to add the worklogs to an already existing user, but that would mean you can no longer…

Hi @elcho and welcome to the Community! That you are not seeing progress is probably linked to the estimation statistic of your board. There is a good chance that it is set to story points, that you are probably not using. Navigate to board settings, estimation and change the setting to issue count (or any other concept…

Hi @Ivan Yeoh Chan Han and welcome to the community! If you want to use smart valiues to refer to custom fields on your issue, you should reference them like this, with an explicit reference to the issue: {{issue.Start date}}

Hi @Madhankumar K, You have probably not granted yourself the appropriate permissions to the new project. Since you plan to migrate issues, it will probably be best to add yourself to the administrator role of the new project before doing the migration. Also, after migrating the issues to the new project, also make sure…

Hi @Dorothy Callahan, Yes, obviously. Moving a ticket is rarely a good idea.Your customers only have access to tickets in JSM through the service desk portal. If you physically move a ticket into another project, the permissions of that other project apply to access that ticket. To access issues in a Jira Software Project,…

Hi @Aaron Merritt and welcome to the Community! Dashboards and shared filters aren't migrated indeed, as you can see from this support article. You can find an overview of alternative methods in this support article. Hope this helps!

Hi @Kristine Gemici, Have a look at Atlas. It's an awesome new tool that covers exactly the communication layer towards stakeholders without all the overhead. Twitter-style. Hope this helps!

Holy crap! I do hope there's enough place to plant all those trees! I am already starting to feel as if there's more oxygen in the air as we speak! 🌳

Hi @Jim Dolan, This is indeed a feature request. It is already listed and you can watch / vote for it here: JSWCLOUD-21708. Hope this helps!