Walter Buggenhout Community Champion

Hi @Tomer_Gal, Mobile for Jira is an app developed by Infosysta. You could best create a support request directly with them. You can find details on how to contact them through their Marketplace listing.

You could use a statement like this: duedate > endOfWeek() and duedate < endOfWeek(1) This would give you the issues with a due date after the end of this week and the before the end of the next week.

There is no predefined shortcut key for that. On a mac (not sure if this will work the same on windows) I managed to get there using the following fun sequence: * press "," (jump to field for editing) * Select the Description field * Press [alt]+[tab] (in my case, this selected 'text' mode) * Press [alt]+[tab] again (to…

That's correct, @Mike Sullivan. You can find pricing for your specific hosting option and user tier through the Marketplace link I included above.

Hi @Muhammad Marhoon, A good starting point might be to check the Hierarchy definition of Portfolio. Check out the documentation on hierarchy configuration here.

As an administrator, type "gg" and in the dialog that appears "Manage add-ons". That will bring you to a list of all installed add-ons. For each add-on, you will also find links to the Marketplace, documentation and so on.

Can you share your board filter and one of the issues that's not showing in your backlog?

Hi @Roberto León Gómez, Good one, right? ;-) It depends; your board is normally based on a filter. If the newly created issue does not match the filter criteria, it will not appear on the board until you make it comply with the filter criteria. Or, the initial status of your newly created issue is not mapped to the columns…

Hi @Chilli Bob, You might get a lot of information from the Version report attached to your scrum board. Or from a different perspective, but also very interesting could be the Release burndown report, definitely since you say you would like to have a view on the situation at sprint start/end.

Each project has Work on Issues permissions in the permission scheme. So basically it is just a matter of setting the desired permissions for Time Tracking in your permission scheme(s) should get you there:

Hi @Mike Sullivan, The previous Atlassian Answers was based on Confluence Questions (now known as Questions for Confluence). You can find it - with a lot more information - on the Atlassian Marketplace. 

Hi @Chris Stauffer, Yes indeed, they are well hidden. Click the Search icon (the magnifying glass) at the top of the side bar. Under BOARDS, select View all boards. There you can find them all.

Hi @Óscar Montero, Each gadget also has a filter behind it. You should ensure that the filters are also shared with your team members.

Hi @i96danma, You can use the following scenarios: * a user has application access to Jira Software, but not to Jira Service Desk (i.e. he/she is not an agent): if you add the user to the Service Desk Team role of a Service Desk project, that will allow him to see issues and comment (internally). * a user has application…

You can create a cascading select as a type of custom field. Which you can then use on your Service Desk portal. To do so, go to custom fields (you need admin permission for that) and add a cascading select field where you define the categories and their sub-categories. Then go to the service desk project and map the field…

Maybe you will need to elaborate a bit more, as "assign a project" can mean different things ... To create a user, you must be a JIRA Administrator. If you are using JIRA's built-in user directory, just head to the Admin section / user management and click Create User. provide the necessary details and grant application…

Exactly!

Hi @AdminTeam EMC, You go to the configuration of your plan (the 3 dots next to your Plan's name) and under Source Data / issue sources click the Edit Sources button. This will take you through the same wizard you used initially to build your plan. In the last step of the wizard, you will see an overview of the issues that…

There is an option to hide the request type indeed, but it will not solve your problem: When you hide a request type from the portal, it will no longer show on the Requests overview page either. Could you explain what you are trying to achieve here or why you would want your customers to add things, but not create issues?…

A bit stupid, but effective and not to use on a regular basis: create a JQL search like Resolution != Unresolved. It will return all the issues you have access to with a resolution filled out. Save it and call it something like 'All resolved issues'. On a dashboard add a Pie Chart gadget, base it on your JQL filter and…

Yes, you did. You are not alone. The quickest way to find it, is click on the magnifying glass (search) in the side bar, and search for it through the view all boards option: Once you have selected it, it will appear in the list of most recent boards under search, as you can see in the above screenshot. The list is…

If you want your agents to create issues on behalf of your customers, they would still be the ticket's reporter and thus still need create issues permission. So no, this does not seem to be a realistic scenario. However, if you just let them keep the create issue permission, everything else you mention would more or less…

Probably I was not clear enough. Proceed as follows: * Open one of your 3 workflows in diagram view * Add the status you want to as your initial status to the workflow (select existing or create a new one) * Drag the Create issue transition from the old initial status to the new status. * Connect any outgoing transitions…

Most likely in the Custom Field configuration (see the documentation) in JIRA. You need administrator permissions for that, so if you are not the administrator yourself, (s)he's the one to talk to.

Your observation is right. Statuses are shared across your entire JIRA instance. You should NOT change the name of a status (unless this is what you explicitly want to achieve). If you need a different status in a workflow, you should not rename an existing status in any way, but select a different status instead, attach…

A first option would be to build a JQL filter to show all issues with linked issues. In your search results, you can display the Linked issues column, which will display all linked issues. Unfortunately, this functionality is not available out of the box, so you will need an add-on for this. For a few options…

Hi Christof, Most of these things are possible through the Atlassian stack (JIRA and Bitbucket). Some items you will need to clarify further (like what you mean by 'discussion boards', sprint view from left to right). The Atlassian ecosystem offers over 3.000 apps in the Atlassian Marketplace that extend the functionality…

--

The best - and probably easiest - way to set this up would be to add a status Workaround Provided (or something like that) to your workflow and use that as a trigger to stop you SLA. As I assume you will not implement a temporary workaround for every Service Desk issue, I would recommend designing the workflow so that you…

Hi @Jason Cox, Could you share a screenshot (or 2) showing where this behaviour is happening?