Comments
-
Да, пойму по-русски. MS Project это совсем другой инструмент. Там нет досок. Я бы сказал, что нужно тогда TFS и MS Project, чтобы получить то, что Jira + Portfolio/Big Picture.
-
If you can not buy an add-on, then you can export issues to a csv file and make such a report in Excel.
-
/rest/api/2/search?jql=reporter = yourreporter or key = TEST-1
-
Hello, You should use the search Rest Api method: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/search-search
-
Hello, Try to add the NOT keyword before the resolution keyword: project in (AB, DEF, GHI) AND NOT resolution changed TO ("Won't Fix", Duplicate, "Cannot Reproduce", "Not A Bug", "Won't Do") AFTER startOfDay(-1) BY currentUser()
-
Hello Yriy, You would need a plugin for it. For example, the Tempo Timesheets plugin: https://marketplace.atlassian.com/apps/6572/tempo-timesheets?hosting=cloud&tab=overview
-
1. Yes. I mean if you do not like changes, you can edit issues. But the history will stay. If you want to make your Jira as if the csv import never existed, then you would need to restore from a backup. 2. You can import without sprints.
-
I do not think that 3 tickets can cause much damage to your system. You can always revert back manually. You will have history for each ticket to revert data. Also I noticed that you try to import sprints. You should provide ids of sprints, not sprint names and sprints must be already created in Jira. During an import of a…
-
Hello, You should enable the Reports feature in the project settings -> Features. Also currently reporting in next-gen projects is limited compared to classic projects. There are only two reports:
-
Hello, You can not let users to see only boards. Because boards select issues by filters, and filters select issues from project, and you give access to projects by project permission schemes. You should modify project permissions so, that users could see only issues in projects, which are selected by the board's filter.…
-
Hello, If you load data from a csv file and there are issue keys in your file, then if an issue with the same key exists, then this issue will be updated. There is a chance that the update will be wrong (I mean logically wrong), and you will have to rollback changes. If you only add issues to Jira, then there should not be…
-
You can not write such queries for custom fields. You would need to develop your own JQL function either by writing your own add-on or use a scripting add-on like Power Scripts or ScriptRunner.
-
Hello I think your JQL query would look like this: status changed to "POC backlog" after 2018-01-01 before 2019-01-01 or status changed to "Modex backlog" after 2018-01-01 before 2019-01-01 or status changed to "Pilot Backlog" after 2018-01-01 before 2019-01-01
-
I used LoadRunner
-
Yes, I meant map.
-
Hello, Make sure that you have not enabled any quick filters in the active sprint screen. Also make sure that the JQL query for the board returns issues, which are missing. You can find the JQL filter for the board in the board settings -> general.
-
Hello, Go to the board settings and enable Remaining Estimate and Time Tracking:
-
Hello, As far as I can see you do not have permissions to edit the issue (there is no edit button). That is why: 1. You should ensure that you can edit the issue. 2. You should make sure that the assignee field is in the Edit screen.
-
Hello, You can not add releases to a next-gen project. By default the board for a next-gen project is a Kanban board. You can enable backlog and sprint in the project-settings -> Features.
-
Hello, If you are a Jira admin, then it does not mean that you can delete any issue. To delete an issue, you must have the Delete Issues permission in this project
-
Hello, If you do not want it to be tedious, you would need an add-on. There are multiple add-ons, which can help you: Power Scripts, ScriptRunner, JTricks, JQL extenstions for Jira. If you want to use the Power Scripts add-on, then your JQL would look like this: key in hasLinks("key in (ABC-123, ABC-234)")
-
Hello, 1. If you do not want a field to be edited, then do not put it to the Edit screen. 2. Use the Field Required validator.
-
Hello, Try to use the gson library. When you create a plugin for Jira, this library is included by default (check if it is included in the pom.xml file). You can find an example here: http://tutorials.jenkov.com/java-json/gson.html
-
Hello, You can develop plugins for Jira Cloud in any language you like. It is not tied to javascript. You can find more info here: https://developer.atlassian.com/cloud/jira/platform/frameworks-and-tools/ You can not run a Jira Cloud add-on on Jira prem add-on. All you can do is i try do develop a library with all the…
-
I gave you general ideas. Unfortunately, I do not have time to make your code work.
-
Hello, What automation do you use?
-
Hello, Create a board. Then create a filter, which would choose issues from multiple service desk projects. For example, you filter could look like this: project in (SD1, SD2, SD3) Then connect this filter to the created board (board settings -> general)
-
Try to connect to Atlassian Support. Atlassian can tell you exact errors: https://getsupport.atlassian.com
-
Hello, You can get such info only for the Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields. You can not get such info for other fields out of the box.
-
Hello, Did you mark the assignee and reporter field in the field configuration during your csv import?