Walter Buggenhout Community Champion

Something strange happened to the question, apparantly. Anyway, I don't know of a single solution that would show everything you mentioned in a single table on a dashboard. But by combining two different gadgets on your dashboard, you should be able to get all the information you want. If you create a JQL filter with all…

Hi @NT, You can use the Projects gadget for this. It does not show the Project Category and Type, but everything else is there, including a list of issue filters:

Are those Epics and Release part of the source data of your Portfolio Plan? Have a look at your Plan settings: * Plan / Configure (through the button with ... next to the Plan's name) * Select Issue Sources from the options on the list * Click the Edit Sources button You will then be guided through the wizard that was…

Hi @mcarreon11, Scriptrunner offers you extended search capabilities that help you do this. Have a look at this related Community question. The answer is the same, all you have to do is modify the parentsOf subquery to something like: "Issuetype = 'QA Testing Subtask' and Status = Closed"

Hi @Deon Myburgh, Out of the box, you can create a new project with a shared configuration (in the create project dialog, you will see the option at the bottom). This will create a new project with the same schemes as your sample project, but it will not include your issues. To fix that, yes you can import issues from e.g.…

Hi @Dror Bernstein, You can't, unfortunately. Tracking work in JIRA is based on standard tasks (issues) and not subtasks. There is a lot of questions and discussion around this topic on the community, e.g. this thread has some interesting background reading around the topic. A common scenario is to use Epics and Stories /…

Hi @sanjay agrawal, Status in JIRA is part of the workflow management system. Take a look the Atlassian documentation on JIRA workflow to get a clear understanding of what it is and how it fits in.

Hi @Rajagopal, JIRA does not have any out-of-the box gantt visualisation of project or resource plans. The marketplace does offer quite a number of add-ons that might help you get there: Gantt add-ons on Atlassian Marketplace 

The formal concept of a 'collaborator' does not really exist in JIRA Service Desk anymore. A collaborator is a member of the Service Desk Team role of your Service Desk project who is not licensed as a Service Desk Agent. So to add someone (who is not a Service Desk agent) as a collaborator, navigate to the Project…

Hi @Laura Casanta, There is not a straightforward way to do this out of the box. What you might do to work around this, is create a create separate filters for each Project Category and instead of using a two dimensional filter statistics gadget, use e.g. pie charts (which offer a nice graphical representation of 1…

Hi @Sowji, I think a good starting point might be the Created vs Resolved Issues gadget you can put on a JIRA Dashboard. This is out-of the box functionality. You can use a saved filter (jql) or a project as its source. By setting the 'days previously' to the desired number of days, you should be close.

Hi @Corey Wentz, What you could do is set up a JIRA project for your projects in the real world. Use a specific issue type for them and call it whatever seems a best fit (project, initiative, big rock, ...). Associate a workflow with your project that represents your project lifecycle (i.e. the stages you mention in your…

Hi @[deleted], Indeed, exporting a dashboard is not something you can do out of the box. But you can export a list of issues from the issue navigator. The included screenshot is from a JIRA Cloud instance, but you should be able to find export options more or less in the same area in your instance too:

A column represtents the status, so no problem there. If you want, you can show the status immediately on the task card itself, as shown here: And regarding the workflow changes: you are right. But I would rather see that as an opportunity rather than a bad thing. Workflow is assigned to issue types and project using a…

You could use the Issue Search instead of the board and have your Project Lead select the assignees there. It might be more effective than trying to use quick filters. You could also use swimlanes on your board to show the issues by assignee as an alternative. But that would only make sense if you aren't using swimlanes…

Those milestones would be the statuses of your workflow. Each status can be mapped to the columns of a kanban (or scrum) board where you will see the tasks listed. This is the core functionality of JIRA. Some key documentation pages: * Workflow configuration * Working with Agile Boards

You should use the assignee's name. e.g. assignee = "Audra Bonacki" (use the naming of the users in your JIRA). I hope you don't have too many users in your project or you will need a lot of filters. Note that the default quick filter Only my issues is already a generic one that shows each logged in user his/her own…

Hi @Rodrigo Santana, No, it would fire at 11 AM, not PM. You should write 23 instead of 11 if you want it to fire in the evening. See e.g. this cron tutorial (with examples).

Your statement refers to the future. It should be >= -120h

Cool idea, but that does not exist yet. Using the labels field is a decent approach to this, given you have some clear guidelines within your organisation on how to manage and use them. Alternatives you might consider is using Flags (available from agile boards) or watching/unwatching issues. The first option will have the…

You could use the labels field for that. You can simply add one or more labels of your choice, search and group by them and use bulk change to remove them afterwards:

I assume you migrated from JIRA 6.x to JIRA Software recently? The Agile menu item has been removed and has become an integrated part of the JIRA Software product. Everything you need is in the documentation over here. When the docs mention 'navigate to the backlog of your desired board', the board must be a scrum board.…

Hi @Ahmed Alghamdi, Sure. You can configure the source of your board using JQL. Assuming you use the issue type 'bug' for your bugs, just select them as the source for your kanban board: Project = <your project> and issuetype = bug ORDER BY Rank (the last part I added so you can change the order of the bugs by drag and…

Hi @Aaron Hicks, Maybe you found out already, but take a look at this similar question.

Hi @[deleted], This is just a list of issues matching certain criteria. All you need to do is go to the issue navigator (Issues - Search for issues), filter out the list of issues you need for each department (see Atlassian documentation for more background) and save your filters so you can reuse them later, when you need…

Hi @[deleted], All of this is indeed possible using JIRA Service Desk (JSD). The only thing that will need some consideration would be the KB per client. Depending on the nature of your services, I assume part of your KB articles are relevant to all of your customers while another part is specific. Through permissions it…

Hi, Make sure you have a transition in your workflow from In Progress to With Development. Or maybe even use a different status to go to when you let customers reopen a ticket. To involve development again, create a new linked issue for them and from there use the same process as during the first iteration.

Hi Josh, If you're on a Server instance, you could do this using the Create on transition for JIRA add-on. It allows you to create a (preferably linked) through a post function of a transition. But be careful about what you mean by dumping the ticket into a different Service Desk and shuffling tickets back and forth. Your…

Hi @Addam Tait, As soon as you add an issue in your overall backlog it will appear on the CFD associated with your board, as long as the filter behind your board does not exclude the issue. So it is not necessary to assign issues to a sprint to have them appear on the CFD. If you don't have too many issues in your backlog,…

Hi @fiorellasantopietro, The trick is not so much in the JQL. What I would suggest is that you use a custom field named something like SLA Calendar in your Service Desk project that you use to set the time of creation. It might have values like: * Office hours * Night * Weekend Depending on how you use SLA calendars at…