Comments
-
What do the log files say the problem is?
-
What app are you using for handling test management in Jira?
-
Black Aliss, George, Morticia and Eskarina
-
Jira doesn't have any function to remove things automatically be default - a human has to actively choose to delete something (or install apps that can archive or delete for them)
-
You do need to put them in a project, as issues cannot exist outside them. But you could have a new project for them, or scatter them into more appropriate projects. For example, if you have a project for "database stuff for the DBA team", you might create issues in there. You can then come up with a way to get them…
-
It's where a stream of updates (usually in code) splits to do a new piece of work. Let's imagine you have some code that is on "version" 42. In the most simplistic stream of development, people will make changes and commit code directly in sequence, so the first developer will commit something and that will be version 43,…
-
Ah, ok, that makes sense. But if Togglr and Jira are both rounding up to minutes, where is there a problem?
-
See https://community.atlassian.com/t5/Jira-questions/Need-REST-API-Details-for-BURN-DOWN-CHART-DATA/qaq-p/1112432
-
Not a role, but you can add people or groups into spaces with read-only access. Have a look at the space permissions, you'll see a swathe of permissions that you do not need to grant (for read-only, tick the first box for "can use" box only, leaving add/edit, delete, attach etc off) Note that you may have an access scheme…
-
I'd use a filter for "fixVersion in unreleasedVersions(xyz) and status = done" (xyz = a project name) to find the issues, then I'd stick the saved filter on a dashboard, in a filter statistics gadget, grouped by version - this will give you a list of unreleased versions with a count of the number of "done" issues in each.
-
I'm afraid that's not a good reason to bother with. Time tracking humans at that level is simply inaccurate, they're never going to record accurately. A few seconds of overhead on each task should simply be considered "overhead", and frankly, ignored.
-
What type of board is it? If it is a Core business board, then issues will disappear 14 days after they have become "done". If you are in a Scrum board, done items will go away at the end of the sprint, and on a Kanban, when you do a release (although if you're using Kanban and don't do releases, you might want to just…
-
The fields do not support tracking in seconds, there's no way to do it with those fields. I have to ask why you're trying to track in seconds? There may be some options, but without knowing why you're thinking in seconds, we can't really tell you if there is a good one for you. (Note that your humans are never going to…
-
Trello uses the word "archive" to mean "we're no longer interested in seeing this on the board". This is ok for a small team with a simple process and no real reporting on what is happening, but it's absolutely the wrong approach in a larger shared system that people are relying on for reporting. Jira's "archive" means "we…
-
Yes, you need settings to tell Jira what database to use. The installation process should be asking you for connection details so it creates it for you. I'm not sure why you are editing setenv.sh for this though, the home directory is set by the installer as well, or if you're doing everything by hand (from a tar.gz file…
-
That's useful background, but does not add enough information to help us to help you. What Jira:Rest library are you trying to use? What do the docs for it say about how to use it?
-
If you create a new project, it will offer you some simple and standard workflows - these are a good starting point to build on!
-
What does the application log say the error is?
-
Yes and no. Yes because Jira is now a composite application. There are three "applications" - Core, Software and Service Desk, all run on the Jira "platform". To keep things simple, you can assume that the platform and "Core" are the same thing. The applications are licenced separately, but there's some inclusivity - a…
-
I suspect you are asking the wrong audience. We're a community of end-users of Atlassian software (including some experts, partners, and Atlassians), and we can try to help you with questions about the software. But your question is about a specific Jira system that you use. We have less access to it than you, and even…
-
This isn't just "best practice" - it is the only way to do it. To change the status of a Jira issue, you must go through a transition!
-
I'm sorry, but there's not enough information her for us to help you much. You have not said what library you want (there's more than one library for Jira REST APIs, perl narrows it, but there's still quite a few options according to a search engine) and you've not said what you've tried or what instructions you are trying…
-
I'm afraid the only way to do this is to move the field editing into the workflow. If you can edit an issue, then you can edit all the fields, the status is irrelevant. If you remove the fields from the create and edit screen, you can't enter data for them, but you can then create transitions that do have the fields on…
-
Jira does not nest projects, you can't have one within another. If you need to break up a big project into bits, but still keep it in one place, then use components to separate the issues into groups. It is usually better to align projects with products when your products have versioned releases.
-
You could do something with a macro, but you would then * be relying on the user to put the macro on the page (or not remove it from the templated text) * still have the users free to rename the page * I'm not sure a macro can edit the page name just by being added to a page, I suspect you'll need to write an app to…
-
What lack of functionality? The boards and filters all allow you to have "closed" issues disappear, while retaining the ability to find them if you need them, so I'm not sure what you are missing?
-
The simple answer is "use the REST API", but I think it might be better for you to start in the middle! I would start with a remote system running a JQL query to fetch the list of issues in the sprint. Probably as simple as "sprint = <name of sprint>" and done via REST calls such as the ones you can find in…
-
I think you may have had a dream, but it's one that may be drawing on several things... * Confluence has some analytics built-in, but turned off by default because it's really flaky on larger Confluences, and is aimed more at debugging than web analytics * There are a number of apps in the marketplace that add analytics…
-
There's no docs on it for Cloud because it is a "restricted function", which means end-users cannot do it.
-
Jira already has two unique ids for an issue, which gives you three options * Use the issue key - gives you a url automatically, https://yourjira/browse/xxx-###. This is not numeric, it's <project key>-<sequence> and can change if an issue moves projects (Although Jira tracks that it has moved, so people landing on an old…