Mykenna Cepek Expert

Every work item (issue) in Jira has a Status field, which can be any of the values in the Workflow for that work item type. Epics have that Status field, and they also have another field called "Epic Status" which can only be "To Do", "In Progress" or "Done". There's some historical reason for this, but I've never fully…

If the parent Story is open, then the Sprint can be closed. The Story and all Sub-tasks will be moved to the next Sprint or to the Backlog as you direct. This is consistent with the Agile perspective of a clear "Definition of Done". The idea with Scrum specifically and Agile generally is that the Story is "atomic" (either…

Jira Cloud has a setting to enable or disable "parallel sprints": When enabled, a Project can have multiple "Started Sprints" (active sprints) at one time. When disabled, a Project can only have one active (started) Sprint at a time. This setting can only be changed by a Jira Administrator, and applies to all Projects in…

First, please clarify if this is a Team-Managed Project or a Company-Managed Project. I'm going to assume it's the latter. Each person listed on the "Project Settings > People" page can be in one or more Role. Project Admins can control which people have what Role in their Jira Project. Roles are defined in a Permission…

Jira Cloud does not offer field-level color highlighting as a feature. You could explore the Atlassian Marketplace for an App which does that. I haven't looked, but I have seen Jira Apps that enable various card coloring options. Note that these Apps will likely have a cost, but you can usually engage a free trial first to…

I find it curious that the error you quoted identifies the field as "Reporter (reporter)" rather than just "Reporter". Maybe that's just Jira being weird in the error message, OR it could indicate that you have a custom field (horribly) named "Reporter (reporter)". Assuming you are a Jira Admin, go to "Admin > Work items >…

I'm using curl from the command line. This one REST endpoint is the ONLY time I've seen bizarre "JSON" like this. I've called many other Jira endpoints that provide well formatted JSON. Try it yourself! You'll see it too: curl --request PUT -k --user you@some.org:personalAccessToken \ -H 'Content-Type: application/json' -H…

I've posted a concern about the response value from one of these new archive-related REST API endpoints. The JSON is, frankly, messed up: https://community.atlassian.com/forums/Jira-questions/Export-Archived-Issues-REST-API-call/qaq-p/2994119

I noticed that the "If/then/else" conditional in Jira Cloud now has an option for AND vs OR with the configured conditions:

Also, the "If/then/else" conditional in Jira Cloud now has an option for AND vs OR with the configured conditions:

Hi @Toon Verschoor, welcome to the Atlassian Community Forums. I'm fuzzy on the problem you're encountering, which makes it hard to suggest things to help or try. Adding screenshots here of what's not working, particularly error messages, can help. Things like "widgets" (gadgets) can be used on Jira Dashboards and on…

Late to the party, but... OPTION 1: Some OR conditional functionality is built-in to some conditionals. Example: "is one of" option in the "Issue fields condition". That can check, for example, if the Assignee is Mary or Bob. OPTION 2: When there is no built-in support, the smart value or() function provides a messy but…

OPTION 1: Some OR conditional functionality is built-in to some conditionals. Example: "is one of" option in the "Issue fields condition". That can check, for example, if the Assignee is Mary or Bob. OPTION 2: When there is no built-in support, the smart value or() function provides a messy but functional alternative:…

We're about to perform our production migration from Data Center to Cloud this weekend. My scripts are working well! A few metrics (yes, I'm bragging here): * 44 projects using automation * 209 enabled automation rules (we are not migrating disabled rules) * Rule export from Data Center was 62,891 lines of (prettied) JSON…

To avoid misleading folks, let's be clear: essentially EVERY single ID will change when importing Jira automation rules to Jira Cloud from Jira Data Center or Jira Server. In my experience, every single rule needs anywhere from a few to dozens of fixes.

I provided some detail on this topic here: https://community.atlassian.com/forums/Jira-Service-Management/Re-Migrate-Automation-from-Jira-Cloud-to-Jira-Data-Center/qaq-p/2964771/comment-id/201548#M201548

Be warned: virtually every ID will be different (only the same as an extremely rare coincidence). The gap here includes IDs for Projects, Statuses, Fields, Transitions, Components, Issue Types, Issue Link Types, Priorities, Resolutions, User IDs, etc. Since automation rules internally use IDs specific to your Jira…

Confluence pages are better about concurrent editing (other editors visible, less likely to lose work, etc). I realize it's not as good as Jira issues doing better at this, but it's an option.

For Company-Managed Projects, check this out: https://community.atlassian.com/t5/Jira-questions/Re-Re-Where-are-the-ProForma-features-in-Jira-Cloud/qaq-p/2914086/comment-id/1080301#M1080301

The documentation (here) says very clearly (last section): You can't delete the default permission scheme. Curiously, it also says this: you can delete the Default software scheme, but this is superficial. Jira will recreate this permission scheme if you create a new company-managed software project, and associate it to…

From Atlassian in '16703: After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-59453 – Ability to Change Default Permission Scheme which has more votes.

Super helpful, @Trudy P Claspill, thank you! It sounds like there is still a need to differentiate JSM from JSW. And I still am not sure what the "W" is for in JSW! :-)

Bummer. I'm guessing that opening a ticket with Atlassian Support might help, where they can get into the Jira database, find the dead boards, confirm that they're not referenced elsewhere in the database, and then delete them. I assume they would be willing to do that. And hey, if enough people ask Support to help with…

@Michiel Schuijer - thanks for your note. I think you are saying that, as a Jira Cloud admin, I can ask Atlassian Support to enable Advanced Forms to enable all (more?) of the ProForma functionality for Forms in Jira Cloud (JSW)? I find the JSW acronym confusing. What does it abbreviate?

If you got this far, please cast a vote for JRACLOUD-85492.

@Arvind Ram - You can use automation to trigger on a new form being submitted, perform other checks, and send email as needed. So: yes!

I'm pretty disappointed to read: We have no current plans to merge with the forms capability available in Jira Service Management and there will be no changes to any site which currently has these enabled for their Jira projects. The acquisition of ProForma provided the opportunity for Atlassian to offer great…

I knew that Atlassian bought ProForma, and intended to incorporate it into their ecosystem. And that's why our org invested in using ProForma at the time because Atlassian made it sound like the best going-forward option (why invest in a different app?). Even the current feature parity doc (which I linked above) doesn't…

Hmmm. So it sounds like a confirmed bug, but it's not clear to me that this ticket outlines the same problem I illustrated above. It might be; might not. For anyone finding this, you could try the potential workaround suggested in the bug ticket, which is to use Confluence Analytics for a date range window of 3 months or…

Native ProForma-like capability is now available natively in Jira Cloud.