Ignacio Pulgar Expert

Besides, you need to have some permissions in the involved projects. In the project of origin, you need to have the following permissions: * Browse Projects * Move Issues In the target project you need to have just Create Issues permission.

You can follow these steps if you have the Bulk Change global permission. * Go to Issues > Search for issues to enter the issue navigator. * Enter your JQL search, ie: project = <project key or project name> * Perform a bulk change: bulk.jpg * Select all issues by clicking on the top-most checkbox and click on Next. * In…

The change was announced some time ago. I agree free is better than $5 / month (min) or $10 / month (max), but anyway, I think it is a more than fair price for a third party addon, and it is much cheaper than any other alternatives...

The addon has recently been changed by this one: https://marketplace.atlassian.com/plugins/timereports/cloud/overview The old addon disappears, together with its gadgets and reports, but you have them available in the new addon.

Your user is likely to lack the 'Transition Issues' permission on the second project. Check that your user has been added to a project role which is being granted such a permission in the underlying Permission Scheme.

You can check the logs by following these steps:* Login with a JIRA Administrator account. * Click on the Cog icon from the top right corner > Applications. * Click on Email Requests on the left menu, under JIRA Service Desk section. * Click on View Log on the right side. * Click on Processing log. Hope it helps.

I don't think so, but maybe you can set a one-character summary via a post function on the first transition (the arrow which starts from the grey circle in the workflow).

Yes, you're absolutely right. Then, the only way would be copying the issue keys in a JQL like: key in (KEY-1,..., KEY-n)

The Sprint Report has a link next to each kind of completions that retrieves the JQL needed. You will see that it is not a pretty function, but a csv of issue keys like: key in (KEY-1,KEY-2,KEY-3) sprint-report-view-in-issue-navigator.jpg

The function most similar to what you want is linkedIssues(issueKey,linkType). In example: issue in linkedIssues(KEY-101,"is blocked by") You might want to add a fixVersion or affectedVersion to this JQL. It's a pity that the issue key is a mandatory parameter.

Have you considered creating a status named 'Impediment' instead of flagging? That way, you will be able to fire the webhook on transitioning the issue to said status. In fact, we have said status on our instance as it is a convenient one on itself.

Then, you might better want to restrict the Reopen transition to users that belong to the Administrators project role instead, and limit who are being given with such a role.

Try: > -7d

Provided that there is no way of doing so out of the box, I've thought of a workaround that you might find useful: * Right before performing the bulk actions, set the affected projects to use no notification scheme (None). * Execute the bulk actions through the API. * Once finished with the bulk actions, set the projects…

Good point, Nic. Do you have a link which explains how to do a bulk edit through the REST API?

Voted for your suggestion and have started watching it.

It would be a good feature. You can raise a suggestion of improvement here: https://jira.atlassian.com

Oh, glad you could finally fix it! Regards

I have configured an issue collector with text multi-line fields without problems: custom-template.jpg

I confirm I can add custom fields to the issue collector normally, with no need for modifying the html or javascript. What are the types of those custom fields?

Are you able to create a new issue through the Create button from the menu on the top and populate those custom fields normally during issue creation?

Are those custom fields present in the create issue screen set on the project?

Hi German, There's no such a thing on Cloud. As a workaround, I would suggest one of these two alternatives: * If it is feasible to grant the users with Administrators project role, then use 'Component/s' field, to which you can add the ones you already know. Project Administrators can add new components by themselves and,…

I bet that's the same on Server, but there you have many more plugin options for automating stuff, like ScriptRunner.

Yeah, only a few system fields can be edited through SD automation rules. Depending on your needs, maybe you can achieve what you need through a built-in post function. Otherwise, maybe there's a post function that might help you in the JMWE addon.

You should open a ticket with Atlassian Support: https://support.atlassian.com/servicedesk/customer/portal/23

If you really want to display so many results and expect them to be less than 1000 open issues at a time, you can search for issues with the following JQL: statusCategory != Done ORDER BY project You can save this JQL by saving it as a favorite filter. Otherwise, Nic's proposed solution will fit your needs.

Yes, you can convert multiple tasks into subtasks: https://jira.atlassian.com/browse/JRA-13245 For doing so, perform a search > bulk change > Move Issues. It is a little bit difficult to find, as logic seems to say that it should be categorized as an Edit Issues operation instead. Hope it helps.

So, you want to get one row per each issue, but you just want to display two columns: the 'Project' the issue belongs to, plus the value of the custom field 'business area impacted'. Is that accurate?

Nice guess. A date that doesn't specify a time defaults to 00:00 hours. So, even a difference of just one hour between server's and user profile's time zones might produce those distinct dates.