I have been using Jira since 6months but haven;t been through any document related to various options available and how to use them for maximum output.
There must be some conventions that help in better tracking of the issue.
For instance, Logging work, Linking issues, creating sub-tasks.
It would be of help if you can share some of the features (and the conventions) that you follow while using Jira. It may vary from team-to-team but there must be some generic rules which can be followed.
Any feedback would be of help. Thanks.
Some of our conventions for using JIRA:
Each project has its own JIRA project.
We use the Greenhopper plugin for Scrum planning.
There is no development without a JIRA issue assigned. If needed, Developer add issues on their own.
Commits contain the JIRA ID (for FishEye integration).
Language of JIRA comments.
When working on an issue, it's state is changed to "in progress"
Findings, Problems, Things Done are documented as comments.
Related answer here.
Related
Is it possible to add SLA (Service Level Agreement) on JIRA Cloud?
I want to add SLA to each ticket right now I don't find any option on Jira cloud. So I'm looking for add/plugin. I did some research but I don't find any add-ons related to Jira Cloud. Some plugins are available but those plugins cannot support Jira cloud.
I stuck here it would be nice if someone suggests any ideas.
Thanks
If you're using Jira Service Desk, they have built in SLAs.
I suppose that you've already found the answer, as this question is quite old. But maybe someone else will look for the solution like this.
So, the answer is yes. You can install plugins for Jira (you can easily find them on Atlassian Marketplace). Among the plugins I would recommend trying is SLA Time and Report for Jira. This add-on can be used for Jira Cloud, Jira Core, Jira Service Management. And it has wide functionality and is easy-to-use. You can find it here.
Hope this will be helpful for someone :)
I have developed a relatively simple Rails web application that others (non-programmers) may find useful. I would like to provide a web interface for anyone who wants to create their own copy of my app and change some minor settings, like the appearance, the name of the app and some of its resources, that type of thing. What kind of technology would allow me to do this? Thank you in advance!
GitHub is probably one of the most popular tools to support this, but there are many others such as SourceForge. I'd start from there and do some research to decide the best one for your purposes.
The best way to collaborate code online is through git. The most popular sites for git management include GitHub and BitBucket. Here's a good article suggesting nine alternatives.
However, you stated it would be used by "non-programmers". I can't tell if they will find it useful through the function of the application or the simplicity of the code, so it seems reasonable to also suggest non-git options.
You could use something like Amazon Web Services or Google Cloud to host the static files. See the AWS S3 docs regarding creating a bucket and adding an object.
If you would like to host the entire application online and allow users to easily edit and view the application in-browser, check out cloud9.
In looking at the Kentico documentation for account and contact management, it seems to give us the ability to create a hierarchy for accounts, such as Account (Client) / Organizational Unit (store locations) / Contact (person at location).
I am looking for a way to accomplish this in Umbraco. We would also want to add multiple fields to the Contact, as they may exist in multiple organizational units.
Is it possible to accomplish this with Umbraco, and if so, how?
There is a free and open-source (according to the latest update from the creator: https://twitter.com/theotron/status/784372313773006849) plugin called Pipeline CRM: https://www.pipelinecrm.co.uk. Source code and installation details are also available on Github: https://github.com/theotron/PipelineCRM.
There's also uSightly, which integrates with Insightly:
https://our.umbraco.org/projects/collaboration/usightly/
I've not used either personally, so I don't know if they would meet your requirements. You can also integrate with other CRM systems yourself if you wish, I know of developers who've integrated with CRMs like Salesforce and Dynamics from Umbraco.
Hope that helps!
I want to add a Ticket System to the web app I'm developing.
The idea is very simple:
Users can open tickets when they have problems and
the Admin can see the tickets the users have submitted.
I'm looking for a ticket system but I have found only systems that are external to the web. I want to add it IN my wep app.
¿Do you know any ticket system por rails?
Thanks
I think using some external gem like noted above would be either an overkill or a hassle due to mentioned bad documentation.
Judging by your problem description this is quite simple to implement.
Create model for tickets and associations with users (I assume you
already have users model fully set up).
Authorize access to tickets' actions depending on user status (admin
or not)
Create corresponding views
P.S.
You could have a look at Redmine code. It is an open source project management software written in rails. I am sure this could give you a good idea of how to build your own or even borrow bits of code from there (if the app license that you are building fits)
Maybe Simple-Ticket would fit you. Though beware the basic implementation and the fact that there is no documentation provided nor written specs.
Have a look at restrospectiva. It doesn't have any documentation though
I would like to have additional fields in Jenkins that would be useful for reporting, for instance team names assigned to the automated tests, so that each team can clearly see their own tests.
Is it possible to add new custom fields to Jenkins reports and if so how can the field values be filled?
edit: Cut question down to make it more specific
There are no answers for this that do not involve nasty workarounds.
Instead, I will a feature request was submitted to the Jenkins project.
(updates here if and when the feature is released)
I had similar problem, and didn't find any straight forward solution. my workaround is to add it to std-out of the test, then it is possible to see it in jenkins later.