Comments
-
Hi @Salim Hammar I assume you click "map field value" checkbox for status column in the wizard. In the final page, you should see the corresponding csv status name and Jira status if status names match expectedly. If not, Jira will create new status.
-
Hi @Alex As I know, scripted field is not written to database. The value of the field is calculated at the time when issue is displayed. So, it is not written to history.
-
Hi @cade.santos Welcome to the community. Did you try to re-produce in different browsers? Is there any error in browser console log? Also, is there a specific error in server log files? Is it applicable for all users?
-
Hi @Yana Doshkova Since it is Cloud version, it could be better to contact Atlassian support team via support.atlassian.com. Because you don't have access to log files etc.
-
It is again the same way. Create a custom field but it shouldn't be text field. For example, create single select cf.
-
Hi @Bryan Tito It is probably a text field. Only pre-defined fields (select list etc) can be given as input in the charts contains statistics like pie chart, issue statistics, two dimensional etc.
-
Hi @Anilkumar Kondapol As I understood, users see two different cancel button in issue view? If yes, delete one of them in the workflow. Can you please share a screenshot for this problem?
-
Hi @Oswaldo Peña Perilla It is not the expected behavior. When you comment in Jira, issue commented event is fired and content of the comment is sent to people configured in notification scheme (assignee, reporter and watchers by default). E-mail is sent but there is no content?
-
Hi @Vijay K Welcome to the community. * Go to Dashboards and create new dashboard * Add Gadget -> Two Dimensional Statistics. * Provide filter and configure dimensions as assignee and status. That's it.
-
Hi @Bo Schlichting Notification schemes (Project Settings -> Notifications) are project based. In that page, issue Updated event is listened for any issue update. When any field is updated, e-mail is sent to the people defined there (assignee, reporter, watchers by default). Workaround could be to disable mail…
-
Hi @MahanthPrudhvi The following property may exist in workflow. It prevents editing issues. Please remove if it exists. Moving an issue to a different sprint requires Edit action for Sprint field. jira.issue.editable=false
-
Hi @James Lebron I haven't tested but it seems there is an open bug for Create operation JRASERVER-26208. Please vote and watch it.
-
I haven't faced this issue before, it is really weird. Glad to hear you solve it. Yes, you should be able to use it properly in free version too.
-
Hi @Minh Nguyen Welcome to the community. Can you please try to create a project with one of the template under Software Development?
-
That's fine. It seems you give 2 working days as a target (2x9). Now you can configure similar automation:
-
Hi @hiltonriddex Welcome to the community. It seems you are not using Jira Service Management Rest Api. Please check this doc. * https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-post Sample: { "serviceDeskId": "10", "requestTypeId": "25", "requestFieldValues":…
-
Hi @Ana Salomon Welcome to the community. Please check the answer in this question: https://community.atlassian.com/t5/Jira-questions/I-do-not-see-any-story-points-in-committed-and-completed-in/qaq-p/1786901
-
Not a big deal, you are welcome!! Have a nice day too.
-
Can you remove "For Current Issue" part? You can look at my previous screenshot.
-
There is a "Choose fields to set.." button between Issuetype and Summary.
-
Hi @Vitalii Voitsekhivskyi Welcome to the community. You can set Epic Link here:
-
Hi @Ste404 SLA will definitely solve your issue. * Create an SLA (ex; Time to response from customer) and use calendar 5/8 (only weekdays). * Configure SLA to count only in Waiting for Customer status and give target - 3 days * Go to automation and use SLA threshold breached trigger. Then transition issue.
-
Hi @Matt Curran First, please confirm that they can see the space. Can be checked from space settings -> permissions. Then, check all parent pages of this sub-page. Because permissions apply from top to bottom. Example; they can not see the sub-page if parent page is restricted.
-
Just to be sure, you edit live workflow in Jira Service Management project, right? Not a Software or business project? If yes, there is something wrong with it and it could be better to create a support ticket to Atlassian for further investigation.
-
Hi @Eoin Flynn I guess it is an inactive workflow. Can you please try to edit the active one (used in service project)?
-
* Go to Workflow -> choose the transition where approval is given * Click Post-functions * Choose Update Issue Custom Field * Select your newly created custom field and paste "%%CURRENT_DATETIME%%" as a value. So, when someone approves, current time will be written to this field. You are welcome.
-
Hi @David Verbeure Yes, you can import from .csv file. Prepare the file as described in this link. * https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html
-
You are welcome. Yes, if you hide a page, it won't be visible.
-
Hi @Ian Dwyer Welcome to the community. Customers do not go to Confluence for articles. When you create an integration, they find them in Jira Service Management search screen. You just need to go to Jira project -> project settings -> knowledge base page and create a link to Confluence space. Please also check…
-
Hi @Ashish G Welcome to the community. By default, notifications are sent to assignee, reporter and watchers. Please go to project settings -> notifications and add Team Member field to events.