Shawn Masters Expert

JWME, an extension for Jira Workflows, would allow you to set a validator in your workflow to block the transition until all issues are Done https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions?hosting=cloud&tab=overview

You would need to get an addon for this. I dont have any scenario's where this is needed but in the past I ran across addons like the one below that might be able to accomplish this for you https://marketplace.atlassian.com/apps/1212247/related-issues-for-jira-cloud?hosting=cloud&tab=overview

Tested this in my own Cloud instance...when i set the variable in the Template it changes in color from Grey to green

Correct, a manager from each department fills out the tickets. Workflow: * Validate ticket info * Create AD / base accounts * Transition the ticket to the next Status; based on on fields used in the ticket linked issues are created to handle things like accesses to development environments, hardware deployed to the desk,…

Ouch, that is one heavy migration. Hopefully you got some projects you can Archive/decommission 

1. Recreate Project A from Server in Cloud server Manally 2. OnPrem- Advanced Search > Query ALL tickets for Project A 3. Export query w/ All fields to CSV file 4. Use Issue import function in Cloud backend and import all tickets into the Project A 5. Repeat steps for each additional project 

Our Server instance was fairly small and mostly used for budget tracking....we exported it all to CSV and imported it back into Cloud relatively easily...had some hiccups around date formatting and some missing Custom fields ....outside of that we didnt see any issues. 

I am actively working on this now...my company used to use a PDF attached to tickets. So i converted that into a ticket type with custom fields for each of the required pieces of information. We then built out Department specific Employee change forms in the customer portal which exposes fields that are needed for each…

Double check your configuration in "Request Types" and make sure that you have the fields all added, based on the screenshot i see it looks like they are only configured to show the summary at the moment 

Changed is not supported but some fields support 'was' which queries a tickets history. Example: Project = 'Foo' and (Status was in "In Progress" AND status in "To Do") Additional Documentation here: https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-764478330.html

Yeah we never found a proper solution for this. We use a combination of Smart Sheets + a Jira Addon called Abacus. The project manager manually inputs values from timesheets submitted to them into a special project we built and Abacus adds formulae functions to the project. They then export the tickets to a third party…

Ah you are using the Portfolio addon, I havent had to tinker with that one much because we have a project manager team that deals with it on my end. It sounds to me like it is rendering the Values ID instead of the actual value. The only way I know to get the values is to interface with the API or to use JWME to extract…

We are on Jira Cloud, had this issue when we first created the service desk and ended up resolving the issue by deleting all the calendars and rebuilding them. Something was causing the SLA to ONLY look at the system default which is that Sample 9-5 you got under yours. 

Does the code look something like this: cf[10026] If so thats a Custom Field or is it only the values that appear as codes? 

What reporting tool(s) are you using? Out of the box? The sprints should reflect the dates you set for them in backlog on the sprint reports. 

Ah understood, I will see if I can recreate it in my own instance and see what i come up with. Did you bring the conditional issue to Atlassians attention? If so, what was their response about it not working as expected? 

Im not sure if they fixed it in Core Jira...the addon i mentioned (JWME) adds a lot of functionality to your workflow transitions and post functions which may have allowed me to bypass your issue. 

I would create a hidden field that Increments up 1 when Denied then have the workflow loop until a condition is met for the hidden fields value to be >= your required value. Can accomplish this with the Addon JWME for Jira

Its been quite some time since i had the same issue ....but I believe you can correct this by going into the Service Desk Project > Settings > Customer Permissions > "Who can customers share with" Set the permission to the 3rd option "Any customer or organization, by searching this project. This option allows them to…

We use a combination of Jira tickets and a linked Confluence Space to do this. The tickets are where the technical jargon is stored and Confluence is where we document the changes and any useful information pertaining to them (Ex: Roadmaps, Prerequisites, dependencies, environments/servers, etc) There are a plethora of…

The last time i encountered this type of error in Cloud, it required a ticket to Atlassian to fix an issue on the backend of our Jira instance. 

Add a step in the workflow to generate a notification to that user would be my first go to. JWME for Jira adds additional functionality to your workflows if would like to accomplish additional tasks. 

Up voting solution - out of the suggestions listed I found Exalate to be quite user friendly and required the least administrative effort to use. 

You can. Many many Support teams utilize this function to escalate issues to higher support tiers. In our own instance I have 2 support teams Internal and External as well as 7 Development teams that work on various products. When our Tier 1 team encounters a bug or feature request they create a linked issue in Jira…

You can reach out to Atlassian and request an Update, but that's about all you can do other than wait on the release to come to your instance. As an admin I have been fielding this complaint with several of my development teams, so we feel your pain. 

Your queries look correct. The only scenario where the sort fails to work in my Jira Cloud instance is in the event the issues are all actually in a "Done" status. This usually happens when the developer/project manager uses an old fixVersion. I would provide you another suggestion which is using a "Filter Result" gadget…

I was able to recreate this exact same issue in my Jira Cloud instance. Looks like a ticket to Atlassian needs to be raised to correct that rendering. 

You could have an automation send out an email to a Predetermined email address, but in Cloud I'm not aware of this being a functionality. 

Are you referring to the Hyperlink next to the status that says "View Workflow" and shows you a pop up window of the workflow the ticket is assigned to? or the actual status transitions? 

The issue navigator is a search tool within Jira. It is used to create filters which are then used to fine tune reports, dashboards, and a myriad of other things. So for example say you get this list of All Tickets that you are looking for. You can save that query as a filter and then use it to display that output in a…