I am using Mantis BT to track my project's bugs and issues. Many issues can only be solved, after other issues have been solved before, so they are blocked by them.
Can I apply a filter that omits all issues that are dependent on not-solved other issues?
Related
In JIRA has three fields (https://jira.atlassian.com/browse/TRANS-1861?jql=)
1. Created
2. Updated
3. Resolved
We can calculate bug fixing time in two ways
1. Bug fixing time= Resolved -Created
2. Bug fixing time=Updated-Created
After fixing the bug, fixing code is tested by tester. If the tester pass the fixing then the bug is closed. Otherwise, developers modify the code and try to fix again. In that case, there is a gap between resolved and closed date. The problem of updated field is the field updated every time someone work on the bug report.
So, I need to know how long time takes a developer to fix a particular bug. If I calculate by this equation (Bug fixing time= Resolved -Created) is it OK?
There are many ways to calculate the bug fixing time, it depends on what are you trying to do and your process. Here are some consideration:
When the bug is reported, when/how do you triage it? Not every bug
reported is a real bug, there are cases where it is work as
designed, training issue or simply enhancement request.
When the bug is assigned, when does the developer start working on
it. Does your developer change the status from New to Working when
they start working on it?
Once the bug fixes is done, how does it being tested? If the test
pass, will the status be changed to Ready?
Once the bug fixes is deployed and validated on production, does the
issue status change to Closed?
To look at the detail of the status changes, you can use the expand=changelog parameter via the REST API and iterate thru the changes to calculate the time in each state. Here is an example:
https://jira.atlassian.com/rest/api/2/issue/TRANS-1861?expand=changelog
I have been developing an iOS app that utilizes the CloudKit feature available for Apple Developers. I've found it to be a wonderful resource, especially since the very day I started designing my backend, the service I was intending to use (Parse) announced it was shutting down. It's very appealing due to it's small learning curve, but I'm starting to notice some annoying little issues here and there so I'm seeking out some experts for advice and help. I posted another CloudKit question a couple days ago, which is still occurring: CloudKit Delete Self Option Not Working. But I want to limit this to a different issue that may be related.
Problem ~ Ever since I started using CloudKit I have noticed that whenever I manually try to edit (delete an entry, remove or add part of a list, even add a DeleteSelf option to a CKReference after creation), and then try to save the change, I get an error message and cannot proceed. Here is a screenshot of the error window that appears:
It's frustrating because anytime I want to manipulate a record to perform some sort of test, I either have to go do it through my app, or just delete the record entirely and create a new one (that I am able to do without issue). I have been just working around this issue for over a month now because it wasn't fatal to my progress. However, I am starting to think that this could be related to my other CloudKit issues, and maybe if I could get some advice on how to fix it I could also solve my other problems. I have file numerous bug reports with Apple, but haven't received a response or seen any changes.
I'd also like to mention that for a very long time now (at least a few days), I've noticed down in the bottom left hand corner of my Dashboard that it is consistently saying that it's "Reindexing Development Data". I remember at first that wasn't an issue, I would get that notification after making a change but it'd go away after the operation is complete. Now it seems to be stuck somewhere inside the process. And this is a chronic issue, it's saying this all the time, even right when I log into my dashboard.
Here is what I'm talking about:
As time goes on I find more small issues with CloudKit, I'm concerned that once I go into production more problems could start manifesting and then I could have a serious issue. I'd love to stick with CloudKit and avoid the learning curve of a different service like Amazon Web Services, but I also don't want to set myself up for failure.
Can anyone help me with this issue, or has anyone else experienced it on a regular basis? Thanks for the advice and help!
Pierce,
I found myself in a similar situation; the issue seemed to be linked to Assets; I had an Asset in my record definition. I and several other I noted reported the re-indexing issue on the apple support website and after about a month it eventually disappeared.
Have you tried resting your database schema completely, snapshot the definition; since you zap it completely and than reset, see inset.
Ultimately I simply created a new project, linked it to cloud kit and use the new container in my original app.
I know there have been many similar issues opened in the past, but I haven't run into this one until very recently.
The deadlock only occurs when my app is launching. I've tried commenting out dozens of lines of code that the stacktrace points to, but the problem doesn't go away. If anyone knows a way to avoid this, that would be awesome. My app depends on being able to run multiple queries on launch, so I can't just get rid of the functionality that's causing the problem.
Here is a partial stacktrace:
I'm not really sure what the problem is, but it definitely has to do with currentUser. Based on previous problems that people have had, it may also be an issue with Facebook login. Either way, this is a really frustrating problem, and I'm not sure how to go about fixing it.
I am using Parse 1.8.0, ParseUI 1.1.5, and ParseFacebookUtils 1.8.0.1
I will post more details if someone can point me in the right direction of where to look.
Edit
Here is a stack trace from a different run. I think the problem has something to do with Facebook authenticating currentUser while I am accessing currentUser elsewhere
How to avoid that that a user has two opened issues in Jira?
It's possible that Jira treat issue management in this way:
when a user has a issue opened and will open another issue, this first one must be automatically paused?
Technically, you can do that with Behaviours plugin.
It needs a Groovy script that looks up the reporter's other issues and transitions them to a paused.
Hovewer, I don't advise doing this, because you'll also need a carefully crafted workflow that supports your "Pause" transition on all statuses, a working Groovy script (needs programming experience, and intense knowledge how JIRA API works). Also needs another script that reopens the previous issue when the newest one is closed, etcetc, there are a lot of pitfalls.
We're writing an application which uses our http api, and occasionally it will encounter errors, failed connections, timeouts, etc.
We'd like to, at least in beta, be able to capture these incidents, and forward them to ourselves somehow. Since obviously many of these issues could be due to the actual connection being down, this would need to queue these incidents and send them when a connection is available.
I tried googling for an answer for this but to no avail, came across a bunch of solutions which catch exceptions, but not just random "incidents" (could really just be a string we log somewhere, we'd just include all the details in it).
Short of writing my own coredata (or something) backed queue, I'm at a loss at what a solution for this could be.
Does anyone know of any libs/services which could help with this?
You might want to look into Testflight, or less general purpose, Parse. Not quite sure, but maybe HockeyKit offers a solution for this, too.
You can take a look at Bugfender, it's a product we have built to solve this problem. We have found that while developing an app there are a lot of issues that are not crashes, so we decided to make our own product to help us on this.
It's easy to integrate and you can get the devices logs. Our service works offline and online, we have spent a lot of time to make it reliable and easy to use.
Compared to other products, you don't need any crash to get the logs, you choose when you want them.