Comments
-
If there's a need to receive email updates as if the user were a watcher in all issues from several projects, the easiest way is configuring a Notification Scheme appropriately, and set it to be used by all the desired projects. Follow these steps: * create a new project role (name it ie: 'notified') * edit the…
-
+1: Very well explained.
-
Here you have some insights that might help you: * The most desirable way of integration would make use of Atlassian Connect. That way, your work could potentially become a new addon for JIRA Cloud that could be commercialized through the Atlassian Marketplace and be preinstalled on all JIRA Cloud instances over the world,…
-
As a workaround, you can attach one lightweight icon image file per each task that needs to be done, with a descriptive filename and image for the task. That way, users would typically have a local folder with the icons of the tasks they are supposed to do frequently, and they would just need to drag and drop the…
-
You should contact Atlassian Support: https://www.atlassian.com/company/contact/purchasing-licensing
-
The boards so linked to a JIRA Core project (and not to a JIRA Software one) is part of Core Labs, and it is currently subject to certain restrictions, including: * Only new projects created with business project template will have access to a board
-
I'm afraid that users need to have Browse Projects permission in the project(s) which issues they need to be able to view/search. You may want to grant access to archived projects just when needed.
-
Besides of Nic's correct point, mind the following: * If the Research type is being suggested before you finish typing it (ie: type = Rese...), that's a good sign of that issue type existing with that name. * If you have selected the Research type from the suggested issue type names, the fact that no issues are being…
-
+1'ed
-
Looks like you need to synchronize one project in two distinct JIRA instances. That might be possible with the help of an addon like Backbone, although I'm not sure whether or not it is currently feasible to synchronize JIRA Cloud with JIRA Server. Have a look at the docs. If both instances can be synced in regard to that…
-
Otherwise, you may create a custom field of type URL in order to store the reference to each other instances.
-
If you need to synchronize data between different instances, you might want to have a look at Backbone addon: https://marketplace.atlassian.com/plugins/com.k15t.backbone.backbone-issue-sync/cloud/overview
-
You may create a custom field for that purpose, which is really easy. In example, you may create a dropdown menu with the values you want. Just go to: https://<YOURS>.atlassian.net/secure/admin/ViewCustomFields.jspa and click on 'Add custom field' on the top right corner. Choose a type like "Single select" field and follow…
-
There are several date fields you can use in your JQL. In example, you can get the list of issues that have been created in the last 90 days: createdDate >= -90d You can use other date fields instead of createdDate (AKA created), like updatedDate or resolutiondate. Alternatively to using -90d, you may also use the function…
-
That wouldn't retrieve hours logged in the last three days on issues created 2 weeks ago... but total timespent of issues created in the last 3 days.
-
For getting that, you need help of an addon. The cheapest one, as well as the one that we use, is Time Reports: https://marketplace.atlassian.com/plugins/timereports/cloud/overview
-
Simply enter the Software project's summary: https://YOURS.atlassian.net/plugins/servlet/project-config/KEY/summary Where YOURS is your Cloud instance's subdomain, and KEY is the project key. After that, click on the Details option, and change Project Type from Software to Core. Finally, click on the 'Save details' button.
-
https://<YOURS>.atlassian.net/admin/users
-
Yes, it is.
-
JIRA Permission Schemes can theoretically be set to grant with Browse Projects permission to the Reporter but, if I'm remembering it correctly, it doesn't work as someone would expect it to behave. How could a user report an issue on a project they cannot see? There might be a potential workaround for that by adding "Group…
-
Add the Resolve issue screen to all transitions to Closed in your workflow. To do so, edit the workflow, click on a transition to Close, and add a screen through the option in the right side. Repeat the process for each other transitions that may go to Closed, and finally Publish your draft. Besides, you can create some…
-
Have a look at the documentation: https://confluence.atlassian.com/jiracloud/configuring-fields-and-screens-735940719.html The diagram is specially useful to understand how it works.
-
Hola Héctor, Te recomendaría leer la documentación: https://confluence.atlassian.com/adminjiracloud/creating-a-notification-scheme-776636401.html Saludos
-
La respuesta de Nicolas es correcta. Se supone que aquí el lenguaje a usar es el inglés. Si necesitas ayuda con la traducción, dime
-
Hi Daniel, Components can be managed by JIRA Administrators (global permission) but also by users with Administer Projects permission (typically granted to the project role 'Administrators' in the permission scheme set on your project(s)). Hope it helps. Regards
-
I would suggest you to try this JQL from the user account that gets the error: project = 11100 Does it retrieve any issues for that user?
-
Ok, that's not doable out of the box in a Scrum board. You could develop your own solution by making calls to the JIRA API, or possibly by using an addon like ScriptRunner for automating that action for you. Kanban's backlog works like you would like it to, once the New status is mapped to the backlog, but then it doesn't…