Comments
-
I think you've misunderstood. Setting the jira.search.views.default.max = 1000 creates an absolute cap which users cannot override by changing the default "tempmax=1000" to "tempmax=<larger number>" - when your search for 1068 runs, it is now running into that 1000 limit and doing exactly the right thing - telling you that…
-
I was trying to say that the reason Atlassian have not implemented it is that they do not think many of their users want to use searches like this. My experience leads me to go along with that.Jamie's users have been different from mine, and obviously had more use for it. So he added it. Much as I'd say my users never…
-
Most people don't care when a coment was made. It's useful sometimes to know when a comment you are looking at was made, and you care about what they've said, but searching by comment date is pretty much unused by almost all users, so no-one has bothered to code for it. I don't think you'll have much problem with…
-
Yes, that's correct.You've used the clause "user". Unless you have a custom field called "user", it's nonsense so the API is ignoring it. I suspect you mean reporter, assignee, creator, watcher or collaborator...
-
You're not far off, try curl -D- -u saravana:xyz -X GET -H "Content-Type: application/json" http://xyz.yza.local/rest/api/2/search?jql=status=TO+DO To get just the id, summary and status (not that you need status, because you know it's TO DO already because that's what you're searching for), add &fields=key,summary,status
-
You don't need to set the resolution as mandatory at all, take that flag off it. What you've done with the workflow is missed either * A post-function to set the resolution * A screen on the transition that has the resolution on it for the user to select One of those two needs to go on to any workflow transition that goes…
-
Nothing. If you have a valid, in-date licence, it's valid for all versions of JIRA released before the end of the licence period. If you don't have a valid licence, you'll need to renew the old one, or buy a new one (depending on how old it is)
-
There is not a lot more I can say. JIRA is not a native test case management tool (the processes for repeat test plans are cyclic procedures, not end to end, so JIRA doesn't have a way to easily manage them) JIRA's heirarchy is intended to be suitable for most users, keeping it simple and clear. You are asking for more…
-
You'll need either the Structure add-on, or a Test Case management add-on that understands your levels.
-
I converted this to an answer because it's a much better follow up to the question I asked, and has better potential to end up as correct and helpful!
-
Is this an add-on for Bitbucket, or have you been changing the installation or source code?
-
Remove the resolution field from all "edit" type screens. It just breaks everything. To clear the resolution, move the issues through a transition with a "clear resolution" post-function on it.
-
It's called Bitbucket Server now, rather than Stash.
-
This is a forum for people working with the Atlassian software suite. While there's a lot of java here because the applications are written in Java, it is not the right place to ask generalised java coding questions. I suggest you look for a more java related place - most people here are not expert java coders (I could…
-
Ok, it would have helped if you'd explained that in the first place. I'd go with Per's answer as the best one - you need to close the issue and have a resolution that indicates why.
-
I assume that you have an issue type of bug, and you have an issue that has been logged as a bug and you want to change its type? If so, then you may be able to edit the field that says "bug" directly, depending on your configuration. If you don't have that option, then you will need to use "move issue", which will ask you…
-
Ok, you're in the wrong place.Answers is for users of Atlassian products. NGINAD is not one of them, it's a product that happens to be using Atlassian Cloud for bug tracking. You'll need to raise this question with nginad, not us. I suspect your best option is to go back there and click "create" to create an issue with…
-
We don't know what your "campaigns", "publisher impressions" and so-on are. Please could you explain what they are in Confluence and what you are expecting it to do with them?
-
No, components are local to projects. Even if you scripted something that added ones with the same name, "Flibble" in project Antarctica is still going to be a different component to "Flibble" in project Galapagos. There are some requests written up for shared/global components and Atlassian have said it's something they…
-
Ok, some more thoughts: I think you definitely need to look at the possibility of a proxy, because there are ways a proxy could do that (and it's the most common way to drop the port number from a url) It's very odd that the url is correct and then gets rewritten - that sounds like something odd is happening on the browser…
-
Ok, that rules out a lot of possible culprits, which is great. When you say you're running JIRA over Tomcat though, does that mean it's just Tomcat? There's no proxy at all? Your url is something like http://ourserver:8080/jira ? One other test - could you clear your cookies in IE and retry it? Does the #i reappear in…
-
That's an interesting one. There's several things it could be, so some quick questions * In your first screenshot, could you hover the cursor over the connectall-9 link in the gadget and see what the url presented there actually is? Or, right click it and select "copy link" and paste it into notepad or a text editor to see…
-
Correct. The simplified workflow does not have much in the way of conditions because it simply cannot know what you might want on there. Your project admins could change it at any time, and the choice Atlassian have had to make is between "map columns, keep it simple for the users" and "every time an admin adds or moves a…
-
Ah, good I'd still have a few words with whomever made the really bad decision, but that's just me (heck, you can still hide it, even if you set it in workflow)
-
No. You can have different field configurations for different projects, and even issue types within projects. >We have a custom field that we track for the status, so the "Resolution" field is always in an Unresolved state That's really not a good way to handle it. Use the resolution properly (At least until Atlassian deal…
-
Have you tried hiding it in the field configuration? >we do not use the "Resolution" field for anything Ah, that's going to break the standard reporting. If you don't use the resolution field, JIRA doesn't know when an issue is done. Even if you hide it, you need to set it.
-
That was what you described in your question, you talked about sub-tasks, which are separate.I'm not sure what version you are using, but I don't lose the edits in 6.4, the history keeps them. Not displayed well, granted, but they're there.The problem with a form of visible notification rather than a lock is that it…
-
Nope, that's not how it works. First of all, the sub-tasks are separate issues. They are linked to their parent, but don't affect it, so having two users work in two totally separate places means, well, that their edits are separate. Second, points 3-5. In point 3, User A files their edits, and that is saved on the issue.…
-
I'd like to emphasise Rodigo's "we do not recommend" sentence. It's correct, but I'd prefer to say it more simply as "Do NOT run the apps in the same Tomcat"
-
Not without a bit of code change - you'd need to change the template rendering the page to remove this I'm not sure why you'd want to go to that effort, it's cosmetic and quite a helpful indicator apparently