Thomas Deiler_db00h3 Community Champion

Dear @David Couillard, Fisheye is not part of Jira. Just the connector is integrated. You do not need to purchase Fisheye a second time. You can link Fisheye to the target Jira, too: FishEye can link to more than one JIRA server at a time, so different teams can work with their own projects in different JIRA Software…

Dear @[deleted], you can restrict this "seeing" of issues with a Issue security scheme. So the staff can be limited just to the monitor-z issues, when set on creation ( can be set as default) So long Thomas

Dear @Dustin, this has nothing to do with curl or anything else. Regardless with which library you communicate with the REST API, you have to follow the rules of the API - that's same for all. Otherwise it wouldn't be an API. So long Thomas

Dear @Muthu first, your team member probably lacks the permission "Modify Reporter" - then he/she can change the reporter afterwards. Bu if your team member cannot modify the reporter and he/she tries to clone, a dialog will appear: So long Thomas

Dear @David Couillard, I don't get it completely. Fisheye doesn't modify Jira issues. It is Jira, that is questioning Fisheye, If it has some issue keys found in the commit comment. Then this information is display in the issue. You should be able to drive your second instance after the import without Fisheye. The Fisheye…

Dear @Doug Kozar, yes, you have to edit one or more files, depending on your previous configuration. Best you go through the "Upgrade Notes" that are always provided, when a new release was done. Please come back, if you need more information. So long Thomas

Dear @Erhan Nacır, when you want that the community helps you as son as possible, then you should provide more information about your current setting, like server configuration, log file extracts or some screen shots. Please do this as soon as possible! Thomas

Dear @Sarra hattab, best you ask this question again on the Developer Community. Thanks for understanding Thomas

Dear @anton satskiy, ether you upgrade your system or you ask the support to assist - but I doubt that they will support this versions. So long Thomas

Dear @[deleted], you mean sharing one account with more users. Sure you can isolate this user just to see only this specific project and no other projects. If you even create a second shared account, you could permit only "Browse Project" to avoid that this user is creating or commenting issue. So long Thomas

Dear @Bas Joosten, best you ask this question again on the Developer Community. Thanks for understanding Thomas

Dear @Guest, neither the subject not the body of your question makes it nearly impossible to write more then an educated guess. Can you please describe you problem in some sentences? Many, many thanks Thomas

Dear @Federico M., first of all, you make "one app" = "one story". The definition of a story can be best explained with the "I N V E S T" model: I = Independent from other stories N = negotiable - not a fixed contract V = of value E = estimatable, small enough to give a good estimation S = small, yo can noting cut of…

Dear @cicob, I have a better idea for you: Make use of the issue collector. This is nothing else than a configuration for a simple web call that can be embedded else where. So long Thomas

Dear @Tushar Tembhare, this is the wrong approach - a story is never assigned to a single individual - it is assigned to a team that committed the story. A sub-task can be assigned to one person. So long Thomas

Dear @Nils Tjøstheim, best you ask directly the vendor about this exception. Thanks for understanding Thomas

Dear @rmatu001, best you ask this question again on the Developer Community. Thanks for understanding Thomas

Dear @Sana Shams, this is the maxResult limit, that is even valid for Jira Server. This parameter can be overwritten, but with caution. It can have massive influence on the performance of the system. To change this for Cloud, you have to create a request - if they agree to increase. So long Thomas

Dear @Customer Test Account, please contact the Atlassian Support, seems something is going wrong. So long Thomas

Dear @fcri, best you ask this question again on the Developer Community. Thanks for understanding Thomas

Dear @Shubh13 best you ask this question again on the Developer Community. Thanks for understanding Thomas

Dear @ODesh, best you ask this question again on the Developer Community. Thanks for understanding Thomas

Dear @Pradeep Panayal, best you ask this question again on the Developer Community. Thanks for understanding Thomas

Dear @Evan Ramos, leave a short trace on each and see where the trace can be found again. So long Thomas

Dear @Dustin, the article describes exactly the case with the REST Api. They just add the third header and leave the others away. Can you check this? So long Thomas

Dear @Janany Satkunam, what you have explained sounds like the natural behavior of Jira. "Children" (sub tasks) are always stuck to their "Parent" (stories) :) It makes sens not to decouple them, because one story should only be done by one team. Eventually it is better to raise the sub-tasks one level up (Story, Task) and…

Dear @AustinS, best you ask this question in the Developer Community. Thanks for understanding Thomas

Dear @Umed Kumar, For Epic I have maintained 5 transition and in board there are 6 column for drag epic from one to other. But story I have required some of column out of 6 in board where I have not required configured screen (date picker). Sorry, I don't get you. Thomas

Dear @Shain Jadhav, there is no single step. You have to do like I wrote. This 'logic' has to be done by you. Rest will just provide the issue information. You can only short it, eventually. The search should already return work log entries, but you have to aggregate them on your own. So long Thomas

Dear @tim.stauffer, somehow you need to flush Fisheye's memory. The solution left: have a look in the DB. But changing this is high risky. I would recommend to contact the Atlassian Support. Because in the end it is a kind of "buggy" behavior. So long Thomas