Comments
-
This is also how you "Translate" the workflow statuses from IT jargon to user friendly verbiage
-
Navigate to the service desk as the Admin Settings > Request Types > Edit Fields If the field is missing from the portal its usually due to permissions or the field missing from the project screens layout.
-
Jira Cloud Admin here We do this with Automation For Jira addon. https://marketplace.atlassian.com/plugins/com.codebarrel.addons.automation/cloud/overview Extremely useful addon and one of addons in the marketplace that is WORTH purchasing for Jira.
-
We had the same issue. We had to open a ticket with HipChat to have the user account deleted from their database. At which point we re-added and no issues since.
-
Cloud or On Prem? Service Desk im guessing? In the cloud version in project settings you can tailor messages to them via 'Customer Notifications' The templates are CSS and HTML format. You control who and when those notifications go out via the project notification scheme.…
-
Sometimes.....the cloud is a bit limited when it comes to comparable addons provided in the OnPrem....a constant issue we face at my company. IF they are custom fields you will need to add those fields. Additionally depending on the version of your OnPrem and how old it is ....the cloud has seen many changes to field…
-
I dont thik the system history tracks Issue Type history. Your going to need to label or find some piece of info specific to those issues that you can use to parse them from the others...like a created date or if they are assigned to you.
-
-
In the sidebar of the project > Project Settings > Delete Project Depending on your permissions the Site Admin may need to delete the project for you.
-
With the JWME it was super easy to add a post function to the ticket creation to strip request participants and other things. We use the Cloud version of Jira so we dont utilize Scriptrunner. I know I see those Adaptivist gents in the forumns all the time helping folks with scripts....i would try raising a ticket with them…
-
Oh and also ensure the data sources include the epics.....i had one group use a JQL query that only pulled sub tasks once....
-
Its been ahwile since ive had to configure Portfolio.....but i think you have to go into the Admin section and add the Epics to the Portfolio Hiearchy first.
-
Need a little clarification.....you want to disable ticket creation on email. But want to ensure comments are still added via email?
-
Depending on how you set things up, you can tackle this 2 ways i know of. 1. Have the exchange/email server remove CC and BCC users. 2. Using an addon like JWME you can have the systems workflow remove or add values to any field.
-
Create criteria to check issues agiasnt then use something like a priority or severity field to assign a 'pain level' to the issue. We do this for our service desk as well. So when a bug is submitted depending on the submitted info the ticket is categorized as one of the following prioritries Project Low Med High
-
In your query for the boards filter you can set an ORDER BY 'field for date here'
-
Below is an example SLA from one of the service desks we use. We are on the cloud.
-
It sounds like you just need a better grasp of the field names so you can write effective JQL. Use your "Custom Fields" admin screen as a reference point for field names to help write JQL queries. Request Type usually refers to the Service Desks customer portal feature. The Service Desk has built in SLA timers. Are you…
-
You could add a specific component or label to those issues, then in the board query set it to look at the issues in the project that != that field value.
-
Linked issue searches are a bit limited currently. There are some feature requests to enhance them which i dont have on hand, we needed a similar search ourselves and found brick walls without an addon. We ended up exporting the data to CSV (excel) to use a pivot table for that report.
-
Thanks Martin, I ll take a look into those. Do they have an addon for managing Budget data or Portfolios?
-
Did anyone find a replacement for Tempo after migration the timesheet addon is absolutely TeRRIBLE
-
Im guessing you checked for Service Desk License and verified their Roles?
-
The report AIO sends doesnt require Jira Acess. Also, no license required for things like RSS feeds.
-
Instead I would add a dashboard with that "Filter Result" gadget. Then setup subsciptions to that board. IF they need to export it they can click the Total issue # at the bottom of the gadget to navigate to the export screen. We use an addon called "AIO (All-In-One Reports)" to build out reports and then setup Cron job…
-
We use RSS feeds and HipChat integration to monitor tickets and updates if your looking to do something like that....
-
Whats your end goal for exporting the tickets?
-
Check the last comment by Vincent Wong on this issue. https://jira.atlassian.com/browse/JSDSERVER-3922
-
Have you tried importing an updated ticket with the corrected SLA into the system?
-
When you get the CSV file downloaded locate the column you dont need select the letter at the top then right click and choose "Delete" It will remove the entire column and shift the data over for you without any tedious edits being needed.