Comments
-
Hi @Sahil Verma Not sure if I understood correctly. You have a list of Jira issues in a spreadsheet and you want to pull other fields from Jira? If this is the case you need to use Jira REST API and write a macro (VBA in Excel or Google App Script in Google Spreadsheet) to pull the data from Jira. or If your issues are…
-
Hi @Sahil Verma You mean you just want these two fields in the export? In that case create a filter with only 2 columns with these fields and export CSV (Current fields). Let me know if this is what you want to do. Ravi
-
Hi @Clive Cartlidge Really interesting question, made me thinking. I don't think this is possible without using any add-on. To solve this problem what I would do is update one additional field (I like using labels) for these statuses (whenever the transitions as done to them) and use that field in the pie chart. Now how…
-
Hi @Laura Kauffman You need to add following transitions. Let us say currently the status of the ticket is In Progress, while it is being tested. * In Progress to Done (Transition name could be Pass) * In Progress to In Development (Transition name could be Fail) In both cases use resolution screen as a transition screen.…
-
It is not a copy but more like a new version of the issue. When you say new field added? Are you talking about the value in the field right?
-
Are you talking about editing values in the existing issues? In that case the new values entered will replace the old ones but there is a history where you can see all the past changes.
-
Hi @Gregor Czempik Whether you would need additional plug-in depends what you are trying to achieve. There are different apps that introduces test management capabilities in Jira - mainly TM4J, Zephyr and XRay. Do you have a list of requirements that you trying to do? how you do test management currently? You can take a…
-
Hi @Deepika When you say form are you talking about the create issue screen that asks the user to fill in the fields? You can modify that screen if you want. Adding new fields to the form won't impact other fields. If that is what you wanted to know. Ravi
-
Hi @OMom2019 Since you mentioned emails check if (you need to be Jira Administrator or ask the person who has those rights). * Your Jira instance has outgoing mail setup. * Check how the project's notification scheme is configured. * Check notification helper to understand why mails are not getting sent. Use dashboards…
-
How are you using the REST API? In which language? For testing the end point you can use curl command or use the Atlassian REST API Browser or use browser plugin to test REST API. Ravi
-
Hi @Michael Küng Did you look at this link. There is an endpoint for creating a component. Ravi
-
Hi @Mahesh Kallepalli There is a really good documentation already on this topic. Also this page explains in depth about creating automation rules. I find it quite intuitive. Start by looking at existing rules but you can go through these pages to get proper steps. Ravi
-
Hi @Rajiv Menon For a true consolidated bird eye view of all the version you would need to use an add-on (paid). The one I personally like is eazyBI. It lets you create variety of reports. Take a look at this sample version report. There are other sample reports showing versions in different charts. Ravi
-
Hi @Mahesh Kallepalli There is already a rule for doing this. Take a look at it. It is based on an SLA (Time to close after resolution). If this SLA is breached that is after x days/hours then ticket will be closed. In automation rule the trigger is SLA breached. Ravi
-
Hi @Rajiv Menon Have you tried Jira Road Map? Use it in in dashboard and configure it to show all projects. It will give a nice summary of various versions across projects with progress bar and summary. It has links to various versions that will take you to a more detailed report. Ravi
-
If you are doing something with JavaScript then you can use customfield_1500, for options it could be either the option id or the option value.
-
Hi @Matt There is a field Script file just above the inline script. Ravi
-
Hi @Mihai Mihai Yes it can be done, before copying the attachment fetch the list of attachments of the linked issue, you will get a list. So before copying search for the file name in that list using list.contains("filename.txt"). If the attachment is found then don't copy. Trying writing the code. Ravi
-
Hi @Balakrishnarao Thota Both are good tools but direct feature by feature comparison is difficult. It really depends what you are trying to achieve, your budget, integration with other tools, resource to maintain it and so on. Do you have a list of things you are looking for from a service desk tool? Ravi
-
Hi @gabe vid Try this code to make Instance field required when Issue Type is either Epic or Story. def issueTypeValue = getFieldById(getFieldChanged()).getValue() def instanceField = getFieldByName("Instance") switch (issueContext.issueType.name ) { case "Epic": instanceField.setRequired(true) break case "Story":…
-
Hi @Anil Were you able to solve the problem? You can also try Project Configurator for Jira it can move the configurations and data between instances. Especially as you mentioned production to staging or vice versa. You can also test the configuration updates before pushing to another instance. Let me know if it helps. Ravi
-
Hi @Mihai Mihai I was able to reproduce. The attachments are listed using their file names but we can sort them using their created date before fetching the last one. Try this code. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.IssueLink import…
-
Let me try to reproduce your last scenario.
-
Hi @Keshni You can move the database to new server along with the application and home directory. Here is the documentation. Ravi
-
No, agile board is another layer on top of Jira Core. It provides additional functionality but if you remove the Kanban board and start using SCRUM board the Issue data and status will stay as it is. Ravi
-
Hi @Stine Lise Ok that good. In that case you can use a label like collector-123456789, this label should be added to the issue that is being raised. Using this label you can write a JQL in your Issue Navigator to filter issues that were raised using Issue Collector. I hope it helps. Ravi
-
Hi @Mickael You are right once you add upto 3 custom fields it is shown under the title on the left hand side, however you can add custom CSS like this below in the announcement banner of your Jira instance. <style type="text/css"> .ghx-plan-extra-fields.ghx-plan-extra-fields-3.ghx-row { float: right; } </style> I hope it…
-
Hi @Spyros Iordanopoulos Just created a new SCRUM board with the same filter as in your Kanban board. Ravi
-
Hi @Sourabh Gulhane Yes there is an ID for dropdown options. You can find it by doing inspect element in your browser .. or .. by going to Jira Administration | Issues | Custom fields | Custom field's Configure option (under Actions) | Edit Option (under Options) and then hovering your mouse over the Edit (under Actions).…
-
Hi @Stine Lise How does this form create issues in Jira? Using REST API? Are you using Jira core, Software or Service Desk? Ravi