Tarun Sapra Community Champion

It's not possible to assign an JIRA issue to multiple assignees. You can have only one assignee per JIRA issue. An work-around for this problem can be to add related people as watcher. Or you can use a custom field of type "Multi user" user picker wherein you can select multiple users.

On every scrum board you will see the option of "view in tempo" which will open the sprint timesheet or the complete board timesheet and then you can create the report. But you need to have the tempo timsheets plugin installed for this feature. 

Use can use Agile timesheet in tempo timsheets plugin https://tempoplugin.jira.com/wiki/spaces/TEMPO/pages/172785792/Agile+Timesheet

try using IssueInputParameters setAssigneeId (String assigneeId) i.e issueInputParameters.skipScreenCheck() issueInputParameters.setAssigneeId("<your assignee id here>")

Just realized that major HTML tags are supported in the wiki markup which is easily supported by confluence - https://confluence.atlassian.com/doc/confluence-wiki-markup-251003035.html 

Yes, Indeed.

Also, the above samples work if you have script runner plugin installed.

In the validation phase of the create transition you will have to check if the custom fields have required values on the linked Issues or not. How to fetch custom field value (since you already have issue Id of the linked issue thus you can get issue object using IssueManager)…

You can add custom fields on any issueType in JIRA. But you need to follow the correct process. Please see step by step guide here https://confluence.atlassian.com/jira064/adding-a-custom-field-720412132.html Make sure you have JIRA admin rights on cloud.

Down for me as well! and not just JIRA REST but the whole website i.e. https://docs.atlassian.com/

Does this solve your query https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-740262715.html

You can export the fields using an plugin - Better excel plugin Integration features * You can export Excel reports directly from the Queue view (with all tickets in the queue). (supported since Better Excel Plugin 2.2.0) * You can export the JIRA Service Desk-specific custom field types, like SLA, Request…

Also while exporting CSV are you selecting "All fields" option?

Based on this ticket, I think it's an open feature request https://jira.atlassian.com/browse/JSDSERVER-826 The exported CSV has columns which follows the format "custom field (< your field name here>)" format So the name of the custom field is included in the bracket.

Thus, you can have a category like "hidden" and other relevant categories.

Hello @Matt Currently, there is no way in JIRA to hide or Archive the project https://jira.atlassian.com/browse/JRASERVER-2785 https://jira.atlassian.com/browse/JRASERVER-1450 The only way is to remove "read-only/ Browse project" permission from the project and that way the project is hidden from all users except the…

Hi @Stefani Kaimakliotou Your requirement of "9956-56" can be implemented with the snippet Pattern.compile("^([-0-9]{5,8})\$") i.e. digits with "-" (dash) and total length of 5 to 8 

Yes, instead of localHost you have to give them an IP address. But using your local machine for production usage is a pretty bad idea. As you should have a dedicated server and an entry in the DNS service to map the IP address to a proper domain name.

If I understand your requirement correctly - you basically want all the Epics which has issues with component name = XYZ. I don't think it's out of the box supported by JIRA. using a plugin (script runner) it's pretty easy. issueFunction in epicsOf("type=story and component = XYZ") The above query gets all epics which have…

Hello @Raju AD - Both CSV importers server different purpose, one is for migrating data ( only for admin thus it includes all fields like parent id etc) other CSV import is for non-admin users and only contains sub-set of functionality and fields. Please see this similar bug reported here about parent id…

Hello Alp, You have an interesting requirement because JIRA does providing Flagging but you can't do much reporting around flagging. i.e. for much time the issue was flagged etc. Since the underlying system of JIRA is built around projects and issues thus my suggestion for you is to create a sub-task type called…

Hello Nigel, It seems the filter used in the gadget has been deleted or made private. If you are the owner of the dashboard which has the gadget then you can click on "edit" option on the gadget (when you hover over the gadget you can click on a arrow pointing downward - top right of gadget and then click on edit). Once in…

Which version of JIRA and Script runner Plugin are you using? Did you try to disable/enable to plugin from the add-ons section

JIRA never imports sub-tasks without parent (via Issues -> CSV or External System import) as that will lead to "orphaned" sub-tasks. Seems like a bug to me. https://jira.atlassian.com/browse/JRASERVER-64768 https://jira.atlassian.com/browse/JRASERVER-64809

Try this issueFunction in subtasksOf('type = story and sprint in openSprints() and assignee !=currentUser() and not issueFunction in parentsOf(" resolution is empty and assignee !=currentUser() ") ') and assignee =currentUser() and status not in (done, cancelled)

Please check if you have a "validator" in create workflow transition of the issue or there are some mandatory fields on the field configuration schemes. Due to these reasons you might not be able to create the issues while importing them from CSV.

I mean if you have a sub-task which is Obsolete, still the user is forced to move it to done column. For lot of teams this is highly unintuitive as when you move an issue to "DONE" column then you see two areas to drop the issues (complete or obsolete) and it's hard to convince SM/POs that even if the issue is obsolete…

It seems you want to copy fields filled in transition screen of one issue into the linked issue. You can write a script in post-funciton to access linked issue and update their fields Here's some samples for updating custom…

Interesting requirement , currently it's an open issue - https://jira.atlassian.com/browse/JRASERVER-4233 I don't think there is a way to avoid creating a new unique issue once you press the "create" button. Only issues which have been created can be part of workflow. Thus, you can put only created issues in a workflow…

Similar questions have been discussed many times on this forum Here's some sample code - https://community.atlassian.com/t5/Answers-Developer-Questions/Scripted-field-get-custom-field-aggrgate-from-linked-issues/qaq-p/491445…