Comments
-
Duplicate of https://community.atlassian.com/t5/Jira-questions/How-do-I-remove-strike-through-s-on-new-issues/qaq-p/797440 which has a lot more information and some answers!
-
Use the call to the backlog to get the backlog, then discard issues that don't belong to the project you are interested in. A backlog is not directly related to a project, so there's no direct call for it. Fetching all the issues in a project is a different story, but you could do that instead, and then discard issues that…
-
No conflicts. It's not "prioritise" with swim lanes and/or filters, it's just about visualising the priorities within the board, but both swimlanes and quick filters can help you use the priorities to re-rank your tasks.
-
Reading status in a script can be as simple as issue.getStatus(), but it depends on where the script is running. Writing a status should only ever be done by scripts that are creating issues during an import of some form. In all other cases, an issue should move through transitions (which will update the status correctly…
-
The heap size is the Xmx setting in the setenv file. Please, don't mess with it unless you're sure you know what you're doing. Throwing memory at a Java problem may not be the right answer and can make things worse. (That said, I wouldn't expect problems from giving any Jira 2Gb heap size, as long as the OS still has…
-
If they are using plain Jira, then they tend to split it up by project. Some projects then use security levels if they're going to want to hide specific things. You can also use the more dynamic features in permission schemes. For example, in old Jira versions "Reporter Browse" in a project used to mean "allow reporter to…
-
It's almost certainly going to be one of the two I've named as the prime culprits: * Remove the resolution field from the create screen * Remove any workflow post-functions on the create transition that set resolution If it's not those two, then check the listeners section in the admin screens for anything that might be…
-
I'm not sure there is anything to "fix". Priority gives you a broad groups of "how important your users think things are", and rank gives you a uniquely ordered list of things that need doing in your board. (By "uniquely ordered", I mean that I can always point at two issues and say one is higher or lower than the other in…
-
Putting the resolution on the edit screen allows you to change it, but not clear it out. (And then has the side effect of causing this problem in the first place, as a user using edit will then be setting it as well) Can you take a look at the history of a really recent issue that has the problem? If there is no mention of…
-
To help you find it, have a look at the history of an issue that has been affected. Exactly when was the resolution set? If the history does not mention resolution, then I can guarantee you it was set on create, so the field is on screen, or you have a post function doing it. For a manual check, click create and check the…
-
No, remove it from the edit screen immediately, you must never do that. That is one of the causes of the problem, and it is going to make it worse. The problem is that you have configured something that is setting the resolution. If you've not added resolution to a screen, configured a post-function or 3rd party or…
-
It's in Jira 7.10 DC, not older versions
-
I'm afraid filling fields won't help. You have to make the configuration for the two issue types you wish to switch between identical - using the same workflows and field configurations.
-
Nevertheless, it is a correct answer. Since it was written, Cloud has had the UI changed to something that makes it a lot harder to find stuff, including the admin sections. Look for the settings cog on the left to start with, while you're in a project view.
-
There are two ways to set a resolution in plain Jira - with a post-function or by simply putting it on a screen that a user goes through (Create, edit or transition). The user will accidentally set the resolution if the field is on Create or Edit, or you've got it on a transition screen on the wrong transition. If this is…
-
No, the levels are set by the level field. There are some uses for a custom field - a level can refer to a user or group picker on the issue, but that won't set the level for you and relies on your users setting them correctly.
-
There is no "trial" software for Atlassian. The licence controls whether it's a trial or a full install. Install the trial and put the current licence into it, and it's a production system. If you're still stuck, then what version are you on?
-
No, because you need to set the level. The custom field is irrelevant.
-
Imagine you have 10 projects, each with an average of 4 different priorities. You now have 40 priorities for everyone to search through. Many users won't know which one is most appropriate for any particular project. Actually, that example works with just 2 sets of 4 priorities.
-
The answer is "yes", but there's some complexity. If your task is a sub-task type (lives below stories), then you will need to use the "convert to issue" option in the options menu. If your task is on the same level as a story, then in some cases (where config is the same, and the type field is on screen), you can just…
-
>set up the security schemes based on this field This can't be done natively. A security scheme is a collection of "levels". Each level is a set of rules for users. (e.g. Top Secret = only people in group X, Secret = people in roles X or Y, and so-on). You have to set a level to apply the rules. Other fields have no direct…
-
I would very strongly recommend using Roles rather than groups. It's more flexible and allows for easier re-use.
-
See the "get issues in backlog" from https://docs.atlassian.com/jira-software/REST/7.3.1/
-
Your App should use web-fragments to do this. Start at https://developer.atlassian.com/server/jira/platform/web-fragments-4227124/
-
REST is by far the best option for talking to Jira, so I'm not sure why you rule it out. But, I'd still take a good look at the off-the-shelf options - https://marketplace.atlassian.com/search?query=servicenow
-
There is no conversion. You have to buy new Cloud services (not licences!) and migrate your data over (if you want to), then let the Server licence lapse. If you got the Server licence accidentally, there may be some value in raising a question with the customer advocates to see if you can get some of it back. If it's…
-
As soon as I think I'm going to start sharing a scheme, yes, I rename it, so it goes into the "shared purpose". I dump the idea of trying to name the projects at that point, it's likely to be "development style X" or "team of people Y work this way" Versioning does help in the short term, in case you make mistakes, or,…
-
I do two things (well, three) Naming by purpose 1: If a scheme is for a project, I use the project key as part of the name (usually the first part). Jira now defaults to creating new schemes for projects with a similar pattern, so the lazy part of me tends to go along with that Naming by purpose 2: If a scheme is to be…
-
Ranking is a unique indicator of where the issue is in the list of all issues in your system. It's roughly equivalent to numbering issues 1, 2, 3, 4, etc, although it's not numbered, as that has all sorts of other problems, and Atlassian abandoned that approach because of them. With Lexorank, it's almost impossible (i.e.…
-
I tend to use ranking. In projects where priority is in use, I'll often use swimlanes or quick-filters on the board to help narrow stuff down by it.