Kelly Arrey Expert

For a report by user, we use Worklogs by SolDevelo. It's very flexible, and the dev team is very responsive.

Hey Phil, "Save As" instead of "Save" indicates that you don't own or have edit permissions to that filter. If you "Save As" a new filter under a new name, and you have admin permissions to the board (I know this works on company managed projects - I can't vouch for team-managed), then you should be able to replace the…

Hi @syee This is on Jira Software Cloud.

Hi @evenings session There are several things you need to check. The permissions helper will do this for you. But if you want to, you can go through it yourself: * Check if the person has any roles assigned in the project * Check if the person is a member of any groups which have roles assigned in the project * Then check…

Hi @Kieran.Heseltine * Click on the Admin gear, top right, and select Apps * Select Manage Apps in the left nav bar (this screen takes a while to populate) HTH, Kel *

Hi @Alexandre The first thing I would check to try and figure out what's going on is to look at the issue history and see which id is logged as having changed the due date back to March 8th.

Rank is a field that implements a relative ranking between tickets by dragging them up or down in a backlog or on a board. You can't edit the rank field to type in a rank value, but drag and drop lets you order the tickets, and then the convention is that the team pulls their next work item from the top of the ranked…

Hi @Tamara I'm an admin too. You could try adding yourself to one of the groups to see if that's what's happening.

Hi @Marcia.Rodrigues you can write a JQL filter for the tickets you want to be notified about, for example: project = HR and type = Task and duedate <3d and status not in (Done, Closed) When you're happy with the filter, save it, then click on "Details" at the top and select "New Subscription". Then you can decide how…

@r2d2 Is this an automation rule? If so, how is it triggered? 

If you have a "Configure" gear at the bottom of the right sidebar, that's where you configure the issue layout. If you don't have it, contact your Jira admin.

@Fiona Brown @Himanshi To be clear "customfield_10001" is an example of the format, right? You'd have to find the actual field ID for the Team field on your own system, right? Thanks!

Hi @Tamara I seem to recall that in some situations you can only specify groups which you are a member of. If that's not what you're seeing, please let me know and I'll delete this answer. HTH, Kel

Hi @Michał Tkaczuk Oh, sorry, missed that. In that case, you could try creating an automation rule with a manual trigger to clone to a different project, e.g., 

Hi @Michał Tkaczuk, it sounds like you are looking for the "Clone" operation. This will copy values to the new issue and link them. There are a couple of ways to find it: * in the filter results view, click on the "..." at the far right and click "Clone" * in the issue detail view, click on the "..." at the top right and…

Hi @Gilberto Vazquez I think the smartvalue needs a format modifier as shown here, e.g., {{now.jiraDateTime}}

@Tamara Tannenberger You may also want to have a look at this page of documentation.

Well, the good news is that the above rule can successfully transition an issue to "In Progress" in a team-managed project. :-) The bad news is that this "In Progress" issue stays in the backlog and doesn't show up in the "In Progress" column on the board. :-(

Hi @Michelle Yip here's an outline of a Jira Automation rule to do something like this, HTH:

Hi @sabina volpicelli, As @Kristján Geir Mathiesen has said, I would recommend against making Late a status. In addition to his suggestion of a custom field, you could: * you could use JCL in a filter or swimlane to identify late issues, e.g., `status not in (Done, Closed) and "Due Date" < -7d` * you could set up an…

@Jack Brickey Is your source current? This is what I see on our Cloud Sandbox:

Hi @Taras Korobko with some help from Atlassian support, I arrived at the following two rules: The important parts are setting the values of the fields: Rule 1: Ticket Implementation Value (PLN): {{#=}} {{Ticket Implementation Value (PLN)}} + {{fieldChange.fromString}} - {{fieldChange.toString}} {{/}} Rule 2: FINAL TICKET…

I tried replicating the example and I think I've got to the same place as @Taras Korobko. I think what's needed is the ability to access both the previous value of "Tester's ..." and the changed value, but I haven't been able to figure out the syntax for that (if it's even possible). Anybody? Thanks

Hi @Taras Korobko If I understand correctly that: * FINAL TICKET VALUE (PLN) is always the sum of the other three PLN fields * The other three PLN fields, i.e., Ticket Implementation Value (PLN), Ticket Testing Value Basis (PLN), and Tester's value by mistakes (PLN), are all input values, i.e., not calculated, Then I would…

<sorry, I need a rethink...>

Hi @Adam LaCoste Not everything from ScriptRunner Server ports seamlessly to ScriptRunner Cloud. You may want to have a look at this: https://docs.adaptavist.com/sr4jc/latest/features/scriptrunner-enhanced-search/comparison-with-scriptrunner-for-jira-server

Hi @Ronnie Legaspi In our workflows, we generally have two "terminal statuses": * Done - we set Resolution to Done on the Done transition * Closed - we display a screen on the Close transition for the user to input a Resolution (and a comment, which you get by default - you don't have to add the comment field to the…

It sounds like one or more Jira "Filters" would do what you need. There's a lot of documentation on this: * basic search * advanced search You could then combine several filters into a Dashboard using "Filter Results" gadgets or other gadgets: * what is a dashboard? * create and edit dashboards HTH, Kel

Hi @[deleted] issuetype = \"Sub Test Execution\" AND issueFunction in linkedIssuesOf("project in (a,b) and issuetype = Defect AND status in (New, Open, "In Progress", "In Test")")

See @Trudy P Claspill's answer.