I would like to do something like:
project = currentProject() ORDER BY createdDate
Is that possible, or can it be added?
There is no "current project" when you're in a search, they execute outside project contexts.
Out of interest, which project would you expect the "current project" to be? JIRA has an internal "last viewed project" concept but it is not surfaced to JQL queries because that would make them non-deterministic.
I would expect the current project to be the one that is displayed in the drop down that appears when you click "Projects" on the JIRA menu bar.
That's the "last viewed", as Robert says. A function for that is not a lot of use in a query, and useless in a saved filter.
I would like to have the "last viewed project" available to JQL.
That would allow me to create a single filter that could be used for any project, and would apply to the last viewed project. (I would not have to create the filter for each project of interest.)
That would be a nightmare - you'd have a filter that could apparently randomly change every time you went back to it. I don't think that's a good idea (I'd certainly hate having to explain it to all the users)
Frank, what are you trying to accomplish with your JQL query? Maybe there is another way to accomplish what you want if we knew what information you were ultimately trying to have at your disposal.
Robert, I would like to view issues in my "currently selected view project" and order the issues by created date, using a saved filter.
I understand that is what you want to do but it is not what you want to ultimately accomplish. Why do you want to do that? What key information would that give you that you seek?
Hi Frank,
you can use the following Plugin to achieve this functionality:https://marketplace.atlassian.com/plugins/com.olegburmistrov.jira.CurrentProjectFunction
It's working like a charm for us.
Best regards,
Tobias
I could use this feature so that I could create a filter that is used by multiple projects - specifically for creating more reusable board filters. Personally, I want to find issues of type = "somecustomtype" + status = "open" + project=CurrentProject where CurrentProject is the project context my board is currently being viewed in. I'd be open to using the CurrentProjectFunction from the plugin below but it isn't supported in cloud.
>CurrentProject is the project context my board is currently being viewed in
Boards are not viewed in a project context. Or rather, the "project context" is "one, many or all projects".
What I want is for the board query to be based on the Project that the board is being viewed in from the user's perspective. My typical user workflow is for the user to select "Project" and then pick a board in that project based. For our company, boards are "Software", "Electrical", "Mechanical". And effectively I'd like to be able to create reusable boards where the query is for the "Project" that is selected. Our users never intentionally go to a board from the "Boards" dropdown.
Since the board can't reuse filters, I get into a lot of duplication right now. For example, rather than "Software" as a board, I need "Project X Software", "Project Y Software", etc. This also means I need to create "Project X Filter", etc. Making both development and execution of a consistent process across multiple projects tedious (the only part that I get to reuse is the 'workflow', I need to manually copy both the boards and filters for each project in JIRA which is an admin headache and prone to manual bugs as a result).
If the filter was able to handle "Project" (and in the case of directly selecting a board, I'd be OK with the result = NULL) then I would have a total of 3 boards, each board would only one filter and I could share this board with every project that shares a given workflow with zero changes. That is what I want to be able to do.
>project that the board is being viewed in from the user's perspective.
Changing the wording "project context" to "the user's perspective" does not change the point. I have a board that shows "issue type = bug". What's the project context or user's perspective there?
In your case it would be "NULL" which is a valid answer to me. In my case (shown here) it would be "SWPD":
ProjectContext.png
Also, I'm not saying that all board queries would need to have an active project context. I just would like to be able to have one for my case, which is in creating a project/context specific query for making a reusable board.
That's wrong. My project context is absolutely not "null", as that's useless. It's "all projects".
Ok, sure so your project argument could be "*" or "ALL" or whatever the JQL equivalent is - sorry, not null. But it doesn't mean that there shouldn't be a solution for the problem I'm facing. I don't see why all of three use cases ("*", "NULL" and "ActiveProject") aren't valid project arguments.
Ok, let's keep it really simple.
You are asking for an answer to the question "what is the current project?"
The answer to that is "none, one, many or all". Your problem is too limited to be usefully "answered" by that. Your three "use-cases" are valid statements, but cannot be turned into useful requirements, and hence should be redefined in real terms or discarded.To do that, you need to work out a way to answer the question: What is the "current project" when I am looking at a board whose filter says "project in (x, y, z)"
I want a filter that says give me issues that match a certain criteria where the project = ActiveProject. From my perspective, ActiveProject is the project specified in the URL via "projectKey" parameter but there is no such property that I can find and filters don't seem to have a way to use the URL parameter as a criteria. I don't want to have to specify a specific value (or even a wildcard) for the projectKey in my filter. This will enable me to create reusable boards that support multiple projects.
I wish this plugin were available for JIRA Cloud.
That's correct - it's because the board defines the projectS it is for.
Again - what is the "current project" when your board filter is "project in (x, y, z)"
There are some add-ons which do "current project" in some places, but it's not based on the board, and can be misleading (because you could be in project w, then go to a board covering x, y and z), and can fail when you are using multiple tabs or browsers.
Thank you, Omar!
For those who aren't clear on the intent behind the question, Omar does a great job of explaining the underlying challenge that needs to be solved for - starting with "My typical user workflow..."
There is only ever one "current project" from a board user's perspective - the one selected in the JIRA user interface.
The idea is to make a board show only issues related to the currently selected project, even when the board query selects from multiple projects.
This would be useful when a board covers multiple projects but we're only interested in the selected one.
I think you've misunderstood the point. You can't answer the question "what is the current project" when you're on a board that includes more than one. There is no "currently selected project" when you're in a board, because the board might have more than one.
The only time "current project" can be answered for a board is when the filter has a project selection clause of "project = X". Which makes it redundant.
Hi @Frank_Spafford If you are using Jira Server you can install the FREE app called JQL Booster Pack throught Atlassian Marketplace and use the requested functionality.After install this app, you should be able to create a query using recentProjects() function, that will allow you to find issues in your recently viewed projects. You can also limit the number of projects retrieved by this function to get the most recent project.You can use the following query to retrieve issues of your currentProject.
recentProjects
• Find issues in my current project:
project
IN
recentProjects(1)
You can find the complete information about this JQL function at its Function Reference page.Kind regards.
In the new Jira experience, a Board always lives within a Project.
Wouldn't it make sense now to allow a Board filter that always queries the Project that the Board lives within? This would eliminate a great duplication of Filters...
No. Because a board might include more than one project.
The move to have boards "inside" a project is understandable, but it's introducing even more confusion for users.
A board does NOT live within a project. A project has a collection of links to boards that might include the project.
Nic,
That seems at odds with what is stated here:
We redesigned the Jira experience to make the relationship between boards and projects much clearer. Now, boards belong to projects, so you can better manage multiple work streams in Jira Software.
Yes, and that statement is wrong.
It's horribly misleading. Boards do not belong to projects.
When a board has a filter like "Project in (X, Y, Z)", which ONE project does it belong to? Nope, can't answer that, because it's wrong. That board does not belong to any one project, it pulls in issues from all three.
Atlassian phrasing it this way has already increased the numbers of people horribly misunderstanding how boards work. It needs to be changed.
Was this ever solved? Still experiencing the exact same thing. Dashboards need a project context drop-down. It could be made optional (locked) and it could inherit last-viewed project upon first load, allowing the user to select a different project in the drop-down (live-type search).
The point is to be able to create a single dashboard--for example, "Sprint Health"--with a bevvy of lovely widgets showing all manner of current-sprint-filtered data. And then to allow that dashboard to be used for any project.
Currently, you'd have to create the filters for each project, save the filters for each project, create a dashboard for each project, add the widgets for each dashboard while specifying the filters for that project.
A colossal waste of time and data! ...if only dashboards had a configurable project context...
As in my reply to Robert, it could be optional (overridden by the queries used in a widget, locked down at the dashboard level...maybe the dashboard has it's own project query which itself could be limited to a query string related to projects and therefore include a single named project, multiple projects based on project attributes, or a "chooser" allowing the user to pick a single project or maybe even multiple projects via Ctrl+Click for the widgets on the dashboard. You could add a separate configuration checkbox to ignore dashboard filter, just in case individual widgets had project filters, so you'd be compatible with current dashboards that are single-query-threaded.
What Omar said, seriously how does Jira not have an option for "Oh your created a new project?" ..." Would you like a board like the other projects in this category or type? great, just click here and we'll copy that board over there just apply this project number for this board!!!" Seriously, stop making other versions of jira and just FIX WHAT YOU'VE ALREADY MADE A MESS OF!!!! GRRR. Sorry today is a day of atlassian rage!
@Robert Massaioli _Atlassian_ I think what the OP wants, or at least what I would like, is when you create a new project from an exist project using the "Share settings with an existing project" When you navigate to that project, and you select "create a new board" (because for some reason this isn't copied as well... WHAT?!?!)On the screen pictured, the hope would be, you would have a either:"Board from existing project, We will swap that project filter for the project where this board will live" or"Board from an existing Saved Filter, we will insert the project where this board will live into the search context of currentProject in this example --> `project = currentProject() ORDER BY createdDate`"I think that's the goal. Currently I have to select one of these last two option, then go edit the filter for this new board with the project I want. If there's another solution to essential clone a board with only swapping the project context, I'd be very interested!!!!!!!!!!! Phil Lanier response above I think makes the use case very clear!
Nic:Other tools, including general purpose tools like Microsoft's SQL manager, application level databases like IBM's ClearQuest, and products like ApTest, all have a notion of the "current database or project"; all have included in their query the ability to reference the "current project (or database)". It is super useful in a saved filter, especially for large organizations.
This is the same reason "Current User" is super useful in a saved filter.
What would change about the filter?
It would work as consistently as "Current User" does.
I like the original posting better.
This modified request only gives me a copy of the queries I have today, modified to fit the new project.
But if we add a field and want to add that to the filter, I would have to update the query in every single project.
We are an organization with over 100 jira projects; just to provide some scope to the issue.
Keep working on this Omar. You are spot-on!!
Lists of issues can be filtered by "Current User".
Why not allow them to be filtered by "Current project"?
Ok, so try this:
That's hard for me to do, because I always log into a project so that I can see what I'm supposed to focus on.
However, imagining the state that you have suggested then the current project would be "*" (i.e. all projects).
I started another thread - https://community.atlassian.com/t5/Jira-questions/Pass-a-URL-querystring-parameter-to-a-dashboard-gadget/qaq-p/1185212#U1187527 a few weeks ago.
I thought I was going mad, missing something obvious with dashboard reuse (or the lack of functionality) but I'm somewhat relieved to find I'm not alone!
Thank you to Jack Nolddor for the JQL Booster Pack recommendation. The recentIssues() method is the best workaround I've found so far!
That's the problem we are trying to solve - we want to scope the results to a project, and we are looking for a way to do that.
Thoughts on how we can accomplish that?
Because there isn't one at the place you're looking at.
We are facing right now the same problem as @Omar Mussa in our projects. Anyone finds a solution for that?
Just found this in the docs, I'm perplexed that none of these threads have mentioned it so far, is this new? Seems to work for me
project = "{{ project.name }}" ORDER BY createdDate
Docs
6 years after, and no solution. This is crazy.
That only works when the automation is working within the context of a specific project. That's fine, but the question here boils down to "what is the current project when I am working outside any context of project?", which can't be answered.
7 years of discussion so we get the accepted answer as "it's not possible", with no suggestion of how to approach the (very popular) problem.
This is so bad.I'll re-send David message (above) for the future generations that'll arrive here:
I think the problem here is that you do not understand what you think you are asking for.
You can "scope the results to a project", that's always been available - you use "project = xyz" in a search.
The problem is that you don't know how to name XYZ dynamically.
It's easy to code a function that would let you do "project = currentProject()" for a search. It's about 12 lines of code.
But for that to work, you need a definition of "current project".
When your user is looking at a search screen, what's the current project? When they are looking at a board that has a filter like "Project in (x, y, z) order by rank asc", what is the current project? When they're on a dashboard which has many gadget filters looking across many projects, what is the current project?
Can you tell me what the current project is everywhere in Jira? (Apart from the obvious ones, where you don't actually need a current project function - the project header, or a single issue view, etc)
It looks like you're new here. Sign in or register to get started.
