Comments
-
You are correct, you will need a custom function for that. Annoyingly, Jira has a "issue was ..." search function, but it does not yet support "project", so you can not yet issue searches like "Project was xyz" Do you have any of the scripting add-ons? Or would you be aiming to write a JQL function as an add-on for…
-
I am sorry to be blunt, but "No process is generated" is incorrect. There is clearly something creating a .dat file and attaching it to the issue when you close or resolve an issue. Jira does not do this natively. If this thing is in Jira, then it is a post-function or listener that your admins have added to it. If it is…
-
People is used in later versions, you're in the right place when you get to "users and roles". The principles have not changed, and it works the same way in people. Your process is mostly right too, and it really is that simple. (Mostly right because the general advice is to use roles and not groups, otherwise you have to…
-
Solved is the word the internet has chosen to say "question is done with" in general. It is not nuanced. In a lot of cases, solved means "solved because there was a fix/solution/answer/help/something", in some cases it means "solved because there's nothing else to do"
-
That's because it has an accepted answer.
-
If you can reach the server over the url internally, but not externally, then either the routing from the outside is not right, or the DNS entry is wrong. What error message do you get when you try to connect?
-
Closest I can get you is text ~ foo and issuetype = story The text keyword makes it search text contents, not just one named fields.
-
You don't actually need to do anything with Tomcat if you want to run it on that url. Change your DNS servers so that http://companyurl.com resolves to 10.1.0.100 and then tell bitbucket to use the named url instead of the ip address.
-
You need to join changeitem to changegroup to jiraissue, reading jiraissue for the issue details, changegroup for date of updates and changeitem to find the change of field data.
-
Atlassian's recommendation is to go to the latest version of Jira before upgrade. Sometimes, you can get away with a little bit lower. For example, at the time of writing where 7.11 is new and on a 0 point release, you could probably get away with 7.10. But I wouldn't recommend risking going lower.
-
There is a table with a pretty obvious name - it is something like moved_issues (but don't quote my memory on that) You'll find it has "old issue key" (the project-sequence key the humans use) then "issue id" (The unique immutable key in the database that does not change when you move the issue to another project)
-
The issue collector gives you some javascript you can add to sires that enable users to raise new issues. Service Desk gives you a service portal, knowledge base links, queues, service level agreements and reporting on all of that.
-
Ok, for Cloud, development is a very different prospect. Start at https://developers.atlassian.com/cloud/jira/platform/getting-started/
-
The problem here is that the error you are getting is only thrown when something else is running on the port. It may well be an old version of the same service that has not stopped fully, but it really does mean there's something there.
-
At a guess, you have the resolution field on the edit screen.
-
It's a column in the "project" table. I can't remember the name off the top of my head, but it is pretty obvious when you look at it (Something like pcounter). Just set it to 0
-
Yes, but that has nothing to do with the question you have asked, so I'm not sure what relevance it has.
-
* Ok, I am not sure that really helps me understand. I do see you want to use it as a help desk to capture things, and I think you want to do it from your website, but after that, I'm lost. I'm not sure what you mean by "intermediate of Jira" However, some guesses: You could use Jira's "issue collectors" - these are bits…
-
No. Not because of the geography but because a Jira Server can only run once. One database and one application. If you want more than one node, you have to move to Jira Data Centre. But this will not help you here either - although in theory you can have nodes geographically separated, in practice this does not work at all…
-
Same again I'm afraid - "java.net.BindException: Address already in use" - there's something running on port 8081
-
Have a look at "help -> About" - the question mark icon in the main interface bar.
-
Jira does not have a way to carry configuration from one system to another, so it's either a large cup of coffee and a manual copying, or you can use one of the add-ons that can export and import config. I'd use Project Configurator to get the configuration across from one system to the other. I am biased on that one - I…
-
In Jira, change the base url to where the users will be accessing it from. You will need to add records to your DNS to direct that address to the Jira server If you want rid of the port number (the 8080), you may need to do a little more by getting Jira's Tomcat to run on port 80 (or, better, 443 with ssl), or using a…
-
I'm afraid we still have to fight. It's always worth it though - once you've got rid of the painful default, the user permissions are simple and intuitive.
-
You will need to define "integrate". While it tells us you want two systems to work together, it tells us nothing more, and is useless as a definition of what you're trying to do. I can't even tell you if you should use the REST interface to talk to Jira or look to build something in Jira from just "integrate". So, can you…
-
No, because you would need to make a different change to every issue, and Jira can't know what change you want to make individually.
-
No, there is no field that does that. It won't work either - think of what happens if you have thousands of issues and change one at the top of the list.
-
You don't need to set up your own Tomcats. Use the installers, they install the Java / Tomcat / Jira or Confluence as a bundle. The "viable solution" is run one installer and then the other.
-
What does the log file say the problem is?
-
No. Jira needs to run on an application server, and the only one Atlassian write for or support now is Tomcat. The installers install Tomcat and Jira bundled together. If you install two Jira systems, you will install two separate Tomcats and a Jira on each one.