Heather Ronnebeck Community Champion

Welcome to the community. Boards in Jira are just different ways of viewing the tickets. You can't close a board when you're done with it, so you'd have to delete it. However deleting the board will get rid of the access to the built in reports for that board. Normally, when I'm done with boards I tend to leave them there…

Sorry for the delay but I do have one more idea. It isn't the nicest but it is one I've used before I had Scriptrunner installed. Basically what you do is pull up a list of tickets updated older than 14 days then sift through them in "detailed view" checking to see when the last comment was made. It's a bit longer and more…

You might have to do this in two steps than sadly. The first step would be to pull in all of your CapEx epics. You will need a JQL similar to: labels in ("CapEx","capex","capEx") and issuetype = Epic Note: The different versions of CapEx is because labels are case sensitive and this will catch more of your possible use…

Thank you for the additional information. Are you using any plugins like Scriptrunner?

Thank you @Bill Sheboy I do sometimes forget that small detail sometimes. 

Welcome to the community. To my understanding the way that the github integration works is that you need to put the ticket number in your pull requests in the respective repo in order to create the connection between the PR and the specific ticket. This allows the flexibility to tie either one repo to one project, or one…

(assignee in (1999, 2000, 2001, 2002 2003) AND project = APPLES AND issuetype in standardIssueTypes() AND status in ("In Progress", "Waiting for customer", "Work in progress") AND (lastCommentedDate >= -14d) order by created DESC So this is returning the error of not having that field existing... Hmm. Let's try this.…

Apologies. It is actually. lastCommentedDate >= -14d So if you substitute out what I had there in the beginning with that line above it should work inside the brackets.

Hello and welcome to the community. You can try the following JQL in your advanced search. epiclink = "XXX" and assignee = currentUser() and labels = "XYZ" Or if you are looking for any epic that is labelled and assigned to the current user, you can do the following: epiclink is not empty and assignee = currentUser() and…

Hello and welcome to the community. It appears that you're using a macro to populate that list in your first screenshot. Which macro are you using to create that table? 

Welcome to the community. You can give this JQL a try: (assignee in (1999, 2000, 2001, 2002 2003) AND project = APPLES AND issuetype in standardIssueTypes() AND status in ("In Progress", "Waiting for customer", "Work in progress") AND (lastComment >= 14d) order by created DESC

While this isn't a community or Atlassian source, I do think that this webpage might help. Please take a look at this approach to doing it. There are some good suggestions like making your workflows on the two projects you are syncing between in the two instances the exact same. https://www.idalko.com/jira-to-jira-sync/ I…

Are you looking to perform a one time migration, or are you looking to set up a constant sync between two instances?

I am not sure how long it will take for the incident to be resolved, but I would wait until it's been resolved to try again. This incident from what I can see is also impacting Confluence Cloud and Jira Cloud products as well. 

Hi @Barış Özer Atlassian is currently experiencing an active incident with their Atlassian Access product. This could be why you're experiencing this. Please see - https://status.atlassian.com/ for more information. Thank you.

Hello @Himil Shah Based on what I am seeing on here - https://www.atlassian.com/software/jira/pricing My understanding is that the free plan is an unlimited free plan, so it just renews monthly be default but won't actually expire. I do not see any limitations on the number of tickets/issues that can be created with the…

Hi @Nazanin Pournouri Normally when I am running an import in Jira server I tend to have a log monitor up and running so that I can see if it is actually still running as the UI tends to not always be ideal in these situations. The Jira imports do take time, so don't be surprised if there are times that it looks like it…

Hi @Markus Kleinschmidt and welcome to the community! There is actually an active Incident going on with Jira Cloud at the moment which they are trying to resolve. (and not a scheduled maintenance sadly). You can follow up the progress here: https://status.atlassian.com…

Hi Markus, I haven't seen this one before, but all I can suggest is perhaps try again after logging out of Jira and logging back in. If that doesn't work try using a private browsing window. There could be a bug in the cached cookies on your device. I hope this helps.

Jira by default is configured to have all users in the same time zone. The easiest way around this is to have your coworker configure his/her profile to reflect their time zone. This link should help with finding those settings - https://support.atlassian.com/jira-software-cloud/docs/manage-your-jira-personal-settings/

Hi, Enhanced Search doesn't support not in which is why you're having issues. What you can do as a workaround is create and saved the enhanced filter to be: issueFunction in linkedIssuesOf("resolution = unresolved", blocks) Then in your advanced filter search enter in the JQL search bar: filter != <name of filter> See if…

You're right that those are the steps you would need to follow. I'm wondering, how did you find the field configuration? Have you tried accessing it through the project settings instead of the Issues Settings? Every project can have its own field configuration scheme and field configurations for each issue type. You'll…

Which type of scheme are you trying to do? Screen? Field? Workflow?

If it's something you want to do going forward you can always create a resolution screen that shows up when transitioning to the state you want to select the resolution on.

You can create a new sub-task issue type to work around this. Once the new sub-task issue type is created you can treat it like any other issue type with the field configs, workflows, screens, etc. This will allow you to keep the regular sub-tasks in their original workflow and other areas. 

Ah yeah that is a bit of an issue. Let me keep digging around then.

This might help - https://community.atlassian.com/t5/Jira-questions/Importing-multiple-Work-Log-entries-from-a-CSV-file-for-a-single/qaq-p/294075

Sadly the best way I can propose doing this is not to migrate at all, but to do a fresh start. 

The date format is actually yyyy-mm-dd so I'd do it like 2021-12-02. Another thing to note is that the dates always go to midnight, so you want your end dates to be the day after your actual end date so it goes until 11:59 pm your server time. So if I wanted to end on Dec 15 for example I'd do resolved <= 2021-12-16…

To measure velocity, I tend to use the created vs resolved JQLs. So I would do: Created project = xyz and created >= start-of-daterange and created <= end-of-daterange Resolved project = xyz and resolved >= start-of-daterange and resolved <= end-of-daterange