Mykenna Cepek Expert

No Jira add-ons are needed to perform the general steps discussed here: * Create sub-tasks on an issue (automatically, or with a manual step) * Automatically close the parent issue when all the sub-tasks are closed Jira Automation can do these steps, with or without a special Issue Type. If you must have a separate…

Have you explored the Epic Report or Version Report?

I've offered 3 solutions here, and this still might be the most feasible one. I like it best because the Accounts can be custom configured on each Project. So "Project A" in Jira could have Accounts "Client A" and "Client A+B+C". Time loggers could easily identify work done in Project A as being only for Client A or effort…

Another potential solution is to use fields on the individual Jira issues themselves to characterize aspects of the billing. This will unfortunately be completely separate from the nice structure in Tempo (Accounts, Categories, etc). But Tempo Reporting can handle Jira fields equally well as Accounts. So there may be…

Check out the "Account Work Attributes" features in Tempo Timesheets. Some potential solutions for your use-case: * Add a simple "Shared Work" checkbox to the "Log Time" dialog. When logging time, folks would check this to indicate the work was shared across clients. Figuring out how to split work tagged this way is pushed…

To answer @Jan Mueller's question: Jira allows "Project Admins" to perform some limited Workflow edits, such as adding/editing Status and Transition elements to a Project Workflow. However, access to Post Functions, Validators, and other deeper configurations of Status and Transition elements is NOT available to "Project…

You'll probably want to use some combination of automation Smart Values for Text fields, to adjust from "...customer name 1" to "...customer name 2". Check out the options in the docs: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ Part of the complexity here is what the "operationX"…

I'm not familiar at all with BigPicture, sorry.

I was struggling with this today also, and @Liam Green's solution worked for me. However, I was able to improve upon it. More below. Note that an assumption here is that you need a "current issue" in the rule to work with. In my case, this was a manually triggered rule. We're using Jira Data Center, and I wanted to put…

A few other thoughts to consider for further experimentation: * Remember that the "Edit issue" action can update multiple fields at once. I'm not sure if that might help avoid triggering your "push to SalesForce" operation multiple times, but it might if you are using multiple "Edit issue" actions in a row. * Separating…

In general, it mostly true that all three Hosting Types of Atlassian products have similar functionality (collaboration and otherwise). But we can't get around the fact that over time Cloud will evolve beyond the Server/Data Center versions more and more in a unpredictable ways over time.

Sounds like you're using Tempo in all the right ways (good job!). But your use-case is tricky. Have you explored creating a separate Account for each set of "customers being split"? Allow me to assume you only want to split billable hours, and that the Product Enhancement applies to customers "A" and "B". Then perhaps…

There are apps to help with this. Here's a discussion of some: https://community.atlassian.com/t5/Jira-Content-Archive-questions/Use-of-Jira-in-Program-Level-management/qaq-p/1872028 One way I have "rolled my own solution" is to rely on "percent complete" of each of the relevant Epics, and just chart that weekly. For one…

Jira doesn't have great ad-hoc reporting built-in. There are plenty of apps in the Atlassian Marketplace that might help you. Instead, I tend to start out with just exporting the data and charting it in Excel (or equivalent spreadsheet tool). Use the standard Issue Search in Jira, set the result columns to include your…

No one here can help "fix this", it's likely something the Tempo app(s) are doing. Those apps are just layered on top of Jira. Reach out to the vendor - the folks who make Tempo. I've worked with them before, they're pretty responsive and good to work with:…

In Jira, open one of the Epics that has blank start/end dates, and then inspect the information in the "History" and/or "Activity" tabs. Look for changes to those date fields, and see if you can identify who or what is changing them. There are lots of possible things that could cause it: * Bulk changes * Apps * Jira…

Reach out to Atlassian support. When my Jira backup wouldn't import, they had to go into the database to fix something in order to get it to work. They're the experts, you've paid for support, let them help.

I'm not sure where you're putting your "formula", but I'm not aware of any standard feature in Jira that would handle something like that. I have two other approaches to suggest: 1) Use a report already built-in to Jira to get what you want. The "Control Chart" in Jira can compute the "average number of days for issues to…

Not really. The results from a JQL query are a true list. And other than having a list entry that looked like a separator (e.g. Summary was something like "--------------------"), there no feature like that in that gadget or any other JQL results list in Jira anywhere that I know of. You might also explore using a…

I see a bunch of answers here trying to address the "visibility" aspect of your requirements - how the results will appear. But I suspect we haven't spent adequate time exploring the filtering/categorization that you need: What I want to achieve is a summary of Time Spent and Original Estimate at Project Level i.e. a sum…

This sounds like some AI vomit, and it's not welcome here.

Then I'd point you to Nic's answer. The board config, most likely the swimlane configuration, is probably wonked.

Also, the "Issue Statistics" dashboard gadget in Jira will give you both counts and a percentage. It's a bar chart, rather than a pie chart, but it might fit your original requirements better. And it takes up less space:

This is rather challenging to do in Jira "out of the box". People typically take one of three approaches: * Export data from Jira and play with spreadsheets (horribly manual) * Set up awkward and complicated Automation Rules (overly complex) * Use a third-party add-on App for Jira that is good at this (added cost) I've…

Go into "Project Settings > Automation" for that project, click on that rule, and click on "Audit Log". What shows there should give you some idea about what's going wrong. Feel free to expand one of those entries to inspect the error, and try to figure out what's going wrong with your rule. If you're still feeling stuck,…

You may have better results contacting the App vendor for your answers: https://marketplace.atlassian.com/apps/1211860/confiforms-data-forms-workflows-for-confluence?hosting=cloud&tab=support Maybe someone here is familiar with that App and can answer your question. But a lot of the folks here will not be familiar with…

I can't speak for Atlassian on exactly why they're trying to differentiate "collaboration" features with Cloud specifically. But I will agree with the next few words there where they differentiate Cloud as better with "innovation" should be given more weight in your evaluation. Atlassian's Cloud offerings are their way…

Are you looking at the same Board as the other users who see something different?

The simplest thing I can think, available in standard Jira (all versions, AFAIK) is to create a new Jira Dashboard, add a Pie Chart gadget, configure it on the project, and select your custom "Checkboxes" field as the "Statistic Type". Here's what it looks like for another "binary" field:

And to help with understanding how to do these kinds of date checks in JQL... The original query: "Target end" > startOfDay() AND "Target end" <= startOfDay(-0d) when translated to words would be: "Target end" date is after the most recent Midnight AND "Target end" is before or equal to the most recent Midnight. No date is…