Walter Buggenhout Community Champion

In a way, Jira IS your tool. The better you configure your workflow with the right screens, conditions, validators and so on, the less your need for additional documentation will become. But aside from that, I get your point. If you need a tool for documentation that works nicely together with Jira, integrates well, then…

Hi @Sandra Meessen, Not within the same Jira Project. A workflow is associated with an issue type. Through a workflow scheme you associate a workflow to an issue type within the context of your project. But as such, the same issue type has a single workflow in a Jira Project. You have two options: * create/use a different…

@Dominic Hobbs, Did you commit your changes from Portfolio to Jira? See Committing plan changes (Atlassian documentation).

That's the cleanest way. If you'd like to automate setting the organisation, you may consider having a look at Automation Lite for Jira (Marketplace app). It has automation rules you can set the Organisation with.

I am getting the impression that you haven't configured any request types for your customer portal yet. Check the Atlassian documentation on how to set them up here.

You cannot use the field on the Create issue screen. To fix your current issue, the quickest way will most likely be to perform a bulk update on your current issues. In issue navigator, search for all issues that are missing the customer request type: Project = <your service desk project> AND "Customer Request Type" is…

Hi @mlanguasco, By default, all tickets created in Service Desk are visible to only the ticket's reporter on the customer portal. For tickets to be visible to other users, they need to be shared with individuals or an organisation. See Atlassian documentation for more info on: * sharing with individuals * Grouping…

Hi @Matthew_Mills, No, that is not possible. An issue type in Jira is either of the Sub-task issue type or of the standard issue type. They are either one or the other. I would recommend to create both issue types: one standard and one sub-task. 

Hi @mlanguasco, Unfortunately not for the moment. There is an open feature request for this functionality that you might want to watch / vote for: JSDCLOUD-826.

Hi @Simon Singh, Two common reasons why they are not showing: * The Customer Request Type field is not filled out. This is required for the ticket to be visible on the customer portal. Make sure to update the field * Through the portal, customers can only see tickets where they are the reporter, tickets shared with them or…

Hi @Idith Eden, There's a couple of functions you can use for fixVersion too, indeed: fixVersion in unreleasedVersions() fixversion = earliestUnreleasedVersion(project) fixversion in releasedVersions() fixversion = latestReleasedVersion(project) For more details, see Atlassian documentation.

Hi @Idith Eden, There's no such thing as a parameter you can use, but JQL has a couple of functions you can use to accomplish your goal: Sprint in openSprints() returns what you describe: your current sprint(s). For reference, there's also these functions: Sprint in closedSprints() Sprint in futureSprints() The first one…

They should most likely be added to the Service Desk Team role, not Developers.

Hi @Lornette Palmer-Rhoden, You don't mention where you want the task to show red. But you could use the field workratio in JQL to filter out issues that go beyond a certain threshold. Just as an example: workratio > 60 will show you all issues where time spent is over 60%. Adjust this to workratio >= 100 and resolution =…

@Dave V, try the following: Project = ITEL and labels = Seals and status != Withdrawn and (Resolution = Unresolved OR resolved >= -5w)

Impressive! Congratz to all!

Great summary and tips, @Daniel Eads {unmonitored account}!

Hi @Steve A Farrand, Can you share a screenshot of what you do see?

Same here; happy first anniversary to ourselves! Cheers and here's to many years to come!

Hi @Helle Overbeck, Just based on status history, not really. But for your specific use case, you could apply the following workaround: status = "Waiting for Customer" and Updated < -2w "Updated" covers much more than just a status change. It includes comments being added, updates to fields, status changes and so on. But…

Hi @Myro, Each individual transition in a workflow comes with the option to associate a specific screen. So every single step from one step to another can have a different screen and set of fields on that screen. So for each transition: * Think which fields you would need to fill out on that transition * Make sure those…

Hi Myro, Apparently this still ís a live question. If I understand your question well, you want to set up an entire out-of-the box repeatable project methodology and framework, including standard work breakdown, document templates, work tracking, probably reporting and so on. As @Matthew Wong has described, part of that…

Hi @Dave Hollinden, I totally understand what you are saying there. About the best practices part, have a look at this community article on issue hierarchy and maybe consider if you really need the sub-tasks. For a very similar use case, we use Epics with Tasks below them. To set and visualise the budget, we are using Epic…

This is opening up Atlassian Certification for a much greater / broader audience!

Nice camera :-)

We adapted the Fibonacci scale in our agile teams to just 0 - 0.5 - 1 - 1.5 - 2.5 - 4. Like @Brett Willson stated, we assume that anything bigger than the Fibonacci 8 point mark is something that needs further elaboration and needs to be broken down into smaller stories. Reporting shows that the bigger stories are…

Hi @Dave Hollinden, If you plan to set things up like this, best practice is to include estimates only on the parent issue and not on the sub-task issues. In the Time Tracking section of your parent issue's detail view, check the tick next to Include sub-tasks as shown below: hours logged on subtasks will be shown here…

Duplicate of this question.

Hi @Justin Song, That's not too difficult to do, but it does take a couple of steps. At high level, you need: * 2 filters to fetch the data for both Dashboard items * A dashboard to display the data on * Suitable gadgets to display the information with From your question, I assume you already know about the existence of…

Thx @Simi S!