Comments
-
The search errors you are getting are down to the network not reaching the services, not the services being down. If you had a port conflict, the Tomcats simply would not start - you'd only ever be running one of the three services at any time, the other two would not start
-
Ok, so that's actually a problem on your network - I assume you are not restarting the applications? The fact they work on one computer and not on another really does scream that there is something wrong with the network somewhere.
-
I'm sorry, I seem to have missed something - you've got this working, but it stops working after it's been up for a while?
-
Sorry, I was unclear on that.You should run the internal systems on different ports - lets say Jira on 8080, Confluence on 8090 and Stash on 7990.You want IIS to listen and respond to port 80 for all three sites. Then when someone lands on the jira site, it talks to jira on 8080 internally.
-
You said you'd skipped step 7 as well as 8. I'm not entirely sure what you've done with 8 - you need the existing connector out and your new one defined, but I think that's what you've done. As long as the old one is gone the route (commenting it out, replacing it with yours or deletion) doesn't matter.Your next step is…
-
The host headers don't change what ports the applications are trying to use or how.Could you go back and do the bits you skipped? Just for one of the applications for now - once we have one working, the others should be modeled on it.
-
Right, you need to change the port number to avoid conflicts, so you need to do the bits you've skipped.
-
You can only run one thing on a port at any time. The point of what you're trying to do is to get IIS to run on port 80 and then gather parts of your site from systems running on other ports.Could you run through the original documentation again to get one of the applications running and explain what you've done…
-
Check your url rewrite rule, and that the url you are rewriting can be reached on the network first, then we'll need the details.
-
Did you follow the actual document, or the comment you've posted which seems to be ignoring most of the document?
-
No, JIRA does not do "field level security". There is an add-on that does a good job of it - Quisapps field security.
-
Depends. If your config was all done in the UI, then it's in the database and you're sorted. If you've customised the application level, then you should have been building it from the WAR, so you can just deploy a copy of the built WAR (and, of course, source controlling the edit-webapp directory, so you can replicate it…
-
Every product owner and project manager I've spoken to has agreed as well. The project structure is wrong here.The tools in Jira Agile for PMs (in both senses) are very very weak. But that's probably correct because when you're doing Scrum or Kanban, you really don't care about that level.In my opinion, it's never been for…
-
Every scrum master I've run this past has winced and said the project structure is wrong.
-
Er, you have not grasped that Howard is trying to describe a broken process. Jira agile does not do this because it does not work.
-
That's the point - you should be defining your boards to cover what you need. If you really do have new projects starting several times a day, then you have probably adopted a project/issue structure that doesn't really work. Or you should be using different board definition filters (a good example is "category = x" -…
-
I understand it fine. What I'm trying to get across to you is 1. You can do this already. But you have to do it manually 2. If you're chanigng the board definition all the time, you're doing it wrong
-
That's not right, you CAN group them by project, which is what the original question was. It's just that you need to write JQL to do it. However - "manually check which projects need to be on the board"? Sorry, no, that's a broken process. Your boards should include the right projects up front. You don't change the…
-
This is a feature request really, not a question. You can do it already, as per the answer originally given, but I think you probably wasn't to raise it at jira.atlassian.comtoo
-
No, I'm afraid you need JQL for each one.
-
It's easy - you just need to define your swimlanes in the Agile board configuration screen - it's got three standard options and you can additionally use JQL as a fourth option.
-
If you hack .jsp files, you should see the changes when you restart Jira However, it might not be the .jsp you want to have a go at. Could you tell us what you're trying to do to the attachment links?
-
Sounds like the user that Jira runs as has a different environment when you start it manually. Who does it run as, and are you using the same account and environment as a system-boot for it?
-
The only issue with taking that route would be if the data structure changed between "cloud" and 5.7.4-standalone. I don't think it has changed at all, so you should be fine.
-
I think the documentation you've got is out of date - the only ones available are the OS-agnostic zip downloads.
-
It is not "required" or mandatory in JIRA-language, it's optional, but doesn't have an empty option. There is no way to do this. The resolution field should NOT be put on create or edit screens, you should remove it from the default screen and others. You should only use it on transition screens on transitions that go into…
-
Yup, that's one way to do it. 1. Create a new group called something like "jira login" 2. Add all your active users into it. 3. Don't use it anywhere else 4. Add it to the global "users can login" permission 5. Keep Jira-users as it is, but *remove it from the login permission* in the global permissions. You are still…
-
There's two things here. First, look at Admin -> Global permissions. You'll see "jira users" in the "can log in" permission. Secondly, look at the project permissions. You'll find that uses "jira users" for all sorts of permissions. The standard thing we tell everyone is don't do it this way. Use "jira users" in the global…
-
Go to Project -> Project Administration and look for "add version" Once you've got one or more versions, the tab will appear. You'll need to be a project admin to get to Project Administration though. It's not automatic for system admins (which is vaguely counter-intuitive, but the right approach)
-
It depends on how people are working. I think most of us are happy with "Open" meaning "workers in the project need to do something about this", which is a logical start for an issue. But a lot of teams have some form of acceptance or triage as well, and having a single "Open" status doesn't cut it for most. That is, they…