Comments
-
Hi @keith_flack, If the statuses in your workflow that you say are after Done are not included in your board filter (or not mapped to your board), that may very well be what is causing your issue. If your scrum board is for a development team, it would make sense (in a way) to consider the Done status the end of…
-
Hi @asosi and welcome to the Commuity! Is there any chance you recently migrated from server to cloud? Just asking since the last comment field is not standard Jira functionality and was often implemented on the server platform via a script field. There is/was a feature request in the backlog that you can find…
-
Hi @Jarrah Hemmant, No. Bulk import of large amounts of issues across multiple projects is restricted to Jira Administrators only. Consider it like this: configuration across multiple projects may be complex and different for many reasons; pulling in a lot of data from an external source may not only create issues, but…
-
There is no limit on automation rules that run within a single project, @Allan Bodgers. That limit applies to global automation rules (that run across multiple projects). And indeed, as @Najm Polaris rightfully mentions, when you move an issue into a Done status the resolution date (resolved if you want to see it in issue…
-
I have not done any imports like that, so can't speak from experience. This KB article describes how to import issue links from csv. It is not clear from the article if it applies to Jira cloud, however. If you prepare your csv file as described in the article, you should be able to confirm if it works once you get to…
-
Hi @Richardson_ Jordan _CGI Federal_, There is no standard measure for the number of comments on an issue, but EazyBI does let you create additional custom fields (in the advanced settings section), where you can use javascript to add the extra information you need: [jira.customfield_comments]name = "Comments"data_type =…
-
Hi @Samuel Pearce and welcome to the Community! This looks like a copybook showcase for Jira Service Management and the included Forms functionality. As it happens, there is a relatively detailed Community showcase article explaining most of what you are looking for. If it is not a perfect fit, I believe it may be a pretty…
-
Hi @Allan Bodgers and welcome to the Community! I am not sure if there is a problem with Jira, but you did run into one (of the) limitation(s) of team managed projects. These have been designed to make the admin experience of Jira projects simpler and accessible to - basically - every Jira user. But that does come with a…
-
Hi @Eri_Ito and welcome to the Community! Changing a field setting from optional to required does not impact any data from the past. But it will impact the behaviour of your screens and worflows (obviously). When you make a field required, users will no longer be able to create or update issues where that information is…
-
Hi @Hannah Schweibert and welcome to the Community! Typically, your milestones are represented in the time dimension of the iron triangle of planning (time - scope - teams). In Jira this is represented by releases (linked to issues via the fixversion field). A release has a start and end date that can be either fixed or…
-
Hi @Agron Morina and welcome to the Community! The short and simple answer is no. A dependency in Jira is implemented through a link between 2 issues. In order to create that link, both issues must exist, otherwise there is nothing to link to. Hope this clarifies!
-
Hi @Alekhya and welcome to the Community! If you can't find validators, that is most likely because you are using a team managed project. That does indeed limit your options a bit. You can add a way to check whether your select field is filled out on a transition in team managed projects using a transition rule. Navigate…
-
Hi @erin_moore and welcome to the Community! To be honest, I am not sure what your use case behind this scenario would be, as I cannot see the value of repeating (the same) project related information on each and every single issue you create in Jira. That seems like a massive ton of overhead. Why e.g. not create a…
-
Hi @Chris F, If you associate the new workflow only to the new issue type, you will be totally fine - as you have seen in the sandbox. Nothing to worry about. Hope this may be reassuring 🚀
-
Hi @Raja rajeswari Gurram 1995, JCMA is the recommended way to migrate by Atlassian. The tool covers a lot of the heavy lifting for you, but migration is not a walk in the park, which may be complicated by the amount of customisation and extensions you have built into your on-prem Jira. This support article gives a good…
-
+1 on @Trudy P Claspill's suggestion to consider first if you want to keep your current Atlassian Organisation as the home for your new site.
-
Hi @Anna Fadel and welcome to the Community! Setting up a new site is very easy. You can just navigate to https://www.atlassian.com/software/jira/free and start a free trial there. You can try any cloud plan (free / standard / premium) for 30 days before you will be billed for the site. Before you do so (or during your…
-
Hi @Don DMack and welcome to the Community! There is a typo in your query: it should be issuefunction instead of issuesfunction. Hope this helps!
-
@Low Darren, Regarding your comment that you don't get an ID when searching: I do not get a Field ID Could it be that you have more than one Team field in your Jira instance? In a test instance, I am getting this for the Advanced Roadmaps field:
-
Hi @Low Darren, It seems that the team field you are referring to is the Team from Advanced Roadmaps. If so, you should search by the team's ID rather than its name. To find out what ID you need for your team, navigate to Filters > Advanced issue search and in advanced search mode type the exact search you are trying to…
-
Okay @Richard Bossenko, Then the following should do the trick: Sprint in (opensprints(), futureSprints()) Yes, an issue that was in a previous sprint is displayed, but that is because the issue was not yet completed in that sprint. I am getting the feeling that there may be something wrong with your expectations here. The…
-
Hi @Svenja Diester, You should be able to come a long way with automation. In this example from the template library you can see how an Epic and all its linked stories can be copied: Hope this helps!
-
Hi @Richard Bossenko and welcome to the Community! Have you tried just the following: Sprint in openSprints() Hope this helps!
-
Hi @Masahiro Morikawa and welcome to the Community! The JQL filter for your board retrieves all issues that you need to see on your board, that means in every status on the board. Because of that, I am not really sure what your requirement is exactly. Do you want to add a quick filter to highlight issues that have been…
-
Hi @Benjamin McClure, If your permissions are set up following best practices, that should not be an issue. That means: if your permission scheme grants the browse project permission to a project role, then there is nothing to worry about. In that case, all you would need to do, is remove the people you are referring to…
-
Hi @Devendar Gangapuram, In addition to what @Rilwan Ahmed already mentioned, a couple of notes: * Technically, moving to Data Center is an option, but the lowest user tier on that platform is 500 users, which seems a lot more than you need. * Cloud is indeed a different product than server and so, yes - you would need to…
-
A few additional variations that may be interesting to consider: fixversion IN unreleasedVersions() That one should show any unreleased versions, similar to this one (which takes the earliest unreleased version into account): fixversion >= earliestUnreleasedVersion()
-
Hi @Sharon Youmans, EarliestUnreleasedVersion() is designed to retrieve only one version: the one that is scheduled next. The tool is not aware of what you consider as major versions or patches. I am not sure what it is exactly that you are trying to get as a result. But if you would like to find all 1.12.x versions, you…
-
Hi @Sharon Youmans If you only want to show the issues in the upcoming release, your filter should be like this (with = instead of >): project = xx AND fixVersion = earliestUnreleasedVersion() Hope this helps!
-
Hi @Fabio Costa and welcome to the Community! I hope you don't mind me answering in English - my Portuguese is not as good as yours ... You can add a workflow property to your workflow transition to either include the resolution options you would like to display or exclude the ones you don't want to see. It depends how…