Walter Buggenhout Community Champion

The Portfolio team is currently working on a new planning experience as well. Although Atlassian - understandably - does not share a full and complete public roadmap online, you can get some insight about what is being worked on right here.

Hi @Darren Bryant, No, that is not possible. By definition, the backlog is the work that is waiting to be started. Once work on an issue starts, it is no longer in the backlog, but work in progress and as such no longer a backlog item. Organisations sometimes have teams doing just analysis work, development or analysis.…

Hi @Michelle Genrich, If you click the Configure Fields button in the top right corner of the Create Issue dialog, see if you have a link to show All fields. Your tabs might appear after clicking that link:

Portfolio for Jira is specifically aimed at managing a multi-project portfolio. It does not look as if next-gen projects will be at that level really soon. Jason Wong, a lead Product Manager for Jira Cloud has recently hosted an Ask me Anything session on this Community. A lot of interesting information about the roadmap…

Hi @Jordan Pesout, There are several possible solutions. The first thing that comes to mind would be Portfolio for Jira. It might be a good idea for you to have a look at this case study to see whether it might help. A lot depends on what your projects look like. How big are they, how do you schedule them (are you an agile…

No @Karina Golkova, Not as far as I know. Release are your milestones and they will always be represented as green/red dots on the timeline. From that perspective, your timeline view is always release-based. You have no visual indicator - however - of the work that is assigned to a specific release on the schedule. I don't…

No, the hierarchy is shared across the entire Jira instance. I don't know if it is relevant to your use case, but you can map different issue types to a single hierarchy level. By default you have * Epics * Stories (and other standard issue types) * Subtasks You can add additional levels above the Epic level and then map…

You are absolutely right, my bad. That should be a comma (,)

I tried a similar search on our own instance and get results with both of these options: issueFunction in LinkedIssuesOf("Project = WhereYourIssuesComeFrom";"is duplicated by") and issueFunction in LinkedIssuesOf("Project = WhereYourIssuesComeFrom";"duplicates") I recommend you try to get the search right in issue…

That's hard to tell without being able to see your data. Can you have a look at an issue that you would expect to see in the filter results and verify how exactly the name of the link is displayed? Is it 'Duplicates', 'duplicate', ... ?

In order to add apps to your Cloud instance, check out Atlassian documentation on that topic. You need to have administrator rights for that.

You can find it on the Atlassian Marketplace. It is a commercial app, so it is not free. If that is a concern, you can search the marketplace for other alternatives, like in this example (searching for linked issues)

Hi @Fernando Souza, Instead, create a standard JQL filter and then use Bulk Change to delete all the issues.

Hi @Wim Horstman, Be aware that this type of search is not native to Jira and requires you to have an app installed that enables this type of search. issueFunction in ... is related to ScriptRunner. So assuming that you have ScriptRunner installed, you could search like this: issueFunction in linkedIssuesOf("status =…

Hi @sri pinninti, There is indeed no 7.11.3 release. I noticed that the issue has also been fixed in 7.12.3, which is the current latest version.

You could use the JQL function in ReleasedVersions() fixversion in ReleasedVersions() and you can limit the search results to the releases of a single project like this: fixversion in ReleasedVersions(ProjectX)

I would first of all reindex and then check whether the issue is still showing on the board.

Thanks for the confirmation, @Jason Wong. I use classic boards on Jira Server / Data Center all the time. My audience consists of teams. And teams, by default, are most of the time working on items in different locations. Some of it is planned, some of it is not. Some is related to customers, other work is internal. Yes, I…

Hi @Jason Wong, Thank you for your reply and the openness throughout this AMA. If I may try to rephrase, next-gen is much more than a design exercise, but really a total refactoring of Jira as a whole. I understand that we are in a pretty early stage of the rebuild. And if I want to work in separate, isolated projects and…

I don't know if this is true for your specific case, but often the JQL filter used to retrieve the data for your board is the cause. If your filter is based on flexible criteria, Jira does not know what projects may be returned in the backlog and more or less requires you to grant manage sprints permission to all jira…

I believe that the goal to 'get people started quickly and easily' with their project is certainly being met. But on the other hand, I have some serious doubt about the 'moving seamlessly between projects' ambition. As each team is free to configure its own project to their liking: * how should we deal with cross-project…

Hey @Cameron Deatsch, Thank you very much for the open and detailed answers over here. There is more to it than just performance. From an administrator perspective and when your goal is to standardise, giving all users the ability to create their own custom fields just sounds like a nightmare. Suppose there was no…

A great improvement in Jira 7.12 is the new custom fields view. We all know the impact of custom fields on instance performance can be really serious. Especially when they are not configured in the best way. Data Center now even has a custom field optimiser, just because of that. Excellent feature, btw! I am wondering how…

With the recent price changes bringing Server so close to Data Center in terms of cost, where lies the future of the Server Platform in - like - 3 to 5 years from now?

Hi @Fabio Manzoni, This is what Custom Field context is for. The extract below from Atlassian documentation describes how to add an additional context for your exception project:

Great update, @Tanya C! Thanks for sharing!

Seems this issue has been fixed for Jira Server in version 7.9 (see JRASERVER-62414)

Hi @romain bonnet, Your Team filter inside Portfolio is based on the Portfolio Team field. So yes, the association should be there. If your Teams are shared teams, it will be possible to assign issues to teams from within Jira as well (see documentation for more info), but by default you would do the assignment from inside…

Hi @miroslav-odstrcilik, You could create a dashboard "My assigned issues" and at several gadgets you configure differently. From the scenario you describe, you can add 2 pie chart gadgets, one showing the issues by label and the other one by project. Or you could just add 1 pie chart gadget and change the view by editing…

Hi Romain, In scope view of your Portfolio Plan and at Epic level, make sure you can see the Team column. I would guess 17 of your epics are not assigned to the THM Team.