You've landed at the right place. oDesk is now Upwork. Learn about the new platform.

Atlassian Jira Jobs

11 were found based on your criteria {{ paging.total | number:0 }} were found based on your criteria

show all
  • Hourly ({{ jobTypeController.getFacetCount("hourly") | number:0}})
  • Fixed Price ({{ jobTypeController.getFacetCount("fixed") | number:0}})
show all
only
only
only
show all
only
only
only
only
only
show all
only
only
only
Looking for the Team App?
Download the New Upwork Team App
Fixed-Price - Intermediate ($$) - Est. Budget: $200 - Posted
A little bit about Hammer Software: We are a shop specializing in software development (system integration, telecom, and networking), telecom, and security/surveillance support. We would prefer to find someone that work out well for a long term partnership, so I would prefer someone that has a larger skillset. You don't have to be perfect, but you should be able to solve the problems with a minimum amount of help. This will be the first rev of the tool. Our client needs it to query a cloud instance of Jira Software (https://xxxxxx.atlassian.net/) with projects set up in Scrum Software Development mode. You must have your own access to a cloud instance of Jira Software. (They have 30 day free trials available.) At this point, I don't care if it's a command line tool (Mac or Linux), desktop gui (must run on OSX El Capitan), or a website that I can host on my own Linux servers (PHP, Python, or perl). What it must do: - provide a weekly report What must be on the weekly report: - show brief (one line) updates on any tickets with 'highest' or 'higher' priority in a top 10 format by developer - should not crash and burn if there are less than 10 tickets matching this - if a given developer does not have any tickets, they should not be listed - should list developer name (first and last name), ticket #, priority as a heading before giving the one line description - should list date issue was created - should list date of last activity - should only consider activity on subtasks, stories and bugs for commits - subtasks, stories, bugs and epics should be considered if they're closed or created, or a status changes from todo to in progress or in progress to done Please detail what language and environment you will use to solve the problem and how soon I should expect a solution from you. Please feel free to ask any questions you need answered to bid on this project.
Skills: Atlassian JIRA Linux System Administration
Fixed-Price - Intermediate ($$) - Est. Budget: $200 - Posted
What is needed is a Jira event listener that detects the creation or updating of a Jira story. When a "create story" or an "update stpry" event is detected, the event listener should retrieve the "template type"(custom field) value from the story. Is should then use the"query issue" REST API to return a list of issues of type "Story Template" within the Jira project of the story and having a "template type" value equal to the one in the story that was created and/or updated. Once the Story Template issue with the correct template type has been identified, use the query issue REST API to get a list of the subtasks of the Story Template issue. use the query issue REST API once more to get a list of existing subtasks for the story that was created or edited. Compare the list of template subtasks against the list of existing subtasks (using the Summary attribute) and add any subtasks that are missing. In user story form: 1) As a user, I wish to create a set of story template issues with subtasks so that I can create stories and have a standard set of subtasks created automatically, so that I can create a story quickly and easily. 2) As a user, I wish to set up different templates for each Jira project, and I wish to be able to set up up at least 5 templates of different types within each project, so that I may have a range of choices as to which set of subtasks should be created automatically. 3) As a user, I wish to be able to enter some subtasks for a story myself and have the event listener fill in any subtasks in the template that are missing from the story. 4) As a user, I wish to do all of this on my current version of Jira (6.3.12), so that I don't have to upgrade Jira in order to use this capability. Project deliverables will include a .jar file suitable for uploading into Jira as an Add-on, plus all source code.
Skills: Atlassian JIRA Java EE
Fixed-Price - Expert ($$$) - Est. Budget: $800 - Posted
We are an app development company with international teams in Vietnam that we are collaborating with. We have recently moved to JIRA as a task organization and management platform to communicate with our team. The problem: lack of easy configuration for time-task reporting and updating. What we need: Expert in JIRA who can organize our platform to allow for time-task reporting that can be viewed by team and individual user. We need someone who can speak with us, understand our needs, and organize the platform for us in JIRA, then sit down and walk us through how the platform is organized. Will need to explain this to our Vietnam Team as well.
Skills: Atlassian JIRA
Fixed-Price - Intermediate ($$) - Est. Budget: $2,500 - Posted
Project: Customer Portal view for internal management system Technologies: Vaadin, JPA, PostgreSQL backend, REST, Pdf.js Time of work: 2 months Startup of project till: february 2016 Tools: Maven Management: Atlassian Jira, Bitbucket, Mercurial, HipChat, Bamboo + AWS, Delivered input data: Functional requirements, Navigation, UX interface design Functional description: Application is a fronted facing customers and getting specific data from internal EAM/CMMS system. Data for application are served through http/REST interface from internal system. Project assumptions: - standard vaadin themes - no need for custom Vaadin components Stories: - application skeleton - Maven skeleton, Vaadin 7.x, local database access JPA/Eclipselink, i18n enabled - portal management login - login window for administrator, language chooser upon login - customer management - customer list, CRUD operation on customer object, customer with up to 10 parameters. After customer creation generate temporaty login data, print/send via email login data. - first login wizard - first login of the customer - wizard after temporary login. First step - customer data fill-in. Step 2 - adding customer user account (up to 5 parameters) - customer login - customer login window, language chooser upon login - customer users management - customer's user list, CRUD operation on the user object, can block user, can send email with invitation/login details - communication with EAM server through REST interface - communication to backend EAM system. Http/Rest interface. - product view - product parameters (up to 20 parameters), product structure (element tree), element view, attached files view, attached service events view. - file view - view of PDF files using pdf.js library. Only PDF files. Depending on attachement properties user can display file and/or print/download file. - service issues view - main summary view of service issues for a given customer. Issue browsing - comments, issue parameters (up to 10 parameters). Expected artifacts: - source code in Bitbucket mercurial repository - unit/integration tests for main controllers (business logic) - work on shared Jira instance with constant log of work
Skills: Atlassian JIRA
Fixed-Price - Intermediate ($$) - Est. Budget: $2,500 - Posted
Project: Data Exchange Service through Spring Integration Technologies: Spring, Spring Integration, Spring Security, Spring Web Services, Spring Web, Spring Web MVC Time of work: 4 months Startup of project till: till may 2016 Tools: Maven, Java Management: Atlassian Jira, Bamboo + AWS, Delivered input data: Functional requirements, Navigation, UX interface design Functional description: Web Application serving as a exchange system for desktop application instances located in different customers. Main use of this system is to transfer data/messages between CMMS systems and monitoring of communication state and delivery/fail states of a transport messages. Stories: - administrators management - administrator view for a global system access. CRUD operations (up to 5 parameters), Enable/Disable administrator. - administrator login - login to administrator view - system settings - email server address - customer management - customer list (data exchange participants). CRUD operation (up to 10 parameters). First time login password for registration purpose. Printing/sending through email first login data. - first time wizard - first time wizard for a new customer. After successful authentication moving to register procedure. Filling basic customer data, generation of RSA keys, saving private key to user desktop, saving public key on the server side. Creation of customer user account. - customer login - customer user login view, choose user interface language. - sync engine - Main sync engine. Using Spring Integration, Spring Web Services. REST interface, data routing, intermediate message monitor, logging of data in local datastore, using http/email endpoints - sync items browser - sync item list, status selection (new, transferred, response received, closed) - customer settings - customer user settings - password change - customer users management - customer users list, CRUD operation for users (up to 5 parameters) - customer communication settings - setting customer live endpoint for active communication Expected artifacts: - source code in Bitbucket mercurial repository - unit/integration tests for main controllers (business logic) - work on shared Jira instance with constant log of work
Skills: Atlassian JIRA
Fixed-Price - Intermediate ($$) - Est. Budget: $2,500 - Posted
Project: Software Update server Technologies: Spring, Spring Web, Spring Web MVC, Spring Security, AWS S3, Jelastic Time of work: 4 months Startup of project till: till may 2016 Tools: Maven, Java Management: Atlassian Jira, Bamboo + AWS, Delivered input data: Functional requirements, Navigation, UX interface design Functional description: Application is a web gateway for updating desktop applications. Installer artifacts are served by bamboo servers and stored in AWS S3 bucket. Delivered service is responsible for serving update data (files) for external customers (hhtp auth) depending on authorization and licence/service rights for a given customer. Project assumptions: - any frontend javascript library. Required responsiveness of a given interface. Stories: - access to artifact data store - communication to AWS S3. One single bucket. Getting data from provided paths and user requests. - administrator login - login window for administrator section. - administrators management - administrator list. CRUD operation for administrator (up to 5 parameters). Active/Inactive flag. - customer management - customer list. CRUD operations for customers (up to 10 parameters). - customer licence management - licence list for each customer (remote user). Licence describes to which S3 path user has access and licence valid date. - update center definition - definition for default S3 paths when there is no customer defined path given during request. - customer login - login window for customer information page. - customer information view - Static html page with links to S3 files/buckets with documentation etc. - licence monitoring - request montoring. Saving http request source and parameters. Browsing through logs with basic filtering (customer, date range). Expected artifacts: - source code in Bitbucket mercurial repository - unit/integration tests for main controllers (business logic) - work on shared Jira instance with constant log of work
Skills: Atlassian JIRA Amazon S3
Fixed-Price - Intermediate ($$) - Est. Budget: $2,500 - Posted
Project: Mobile/Desktop application for remote work for CMMS/EAM system Technologies: Java, JavaFX, Protobuf, H2 database Time of work: 4 months Startup of project till: till march 2016 Tools: Ant, Maven, SceneBuilder (FXML), Ruggget Tablets Management: Atlassian Jira, Bamboo + AWS, Delivered input data: Functional requirements, Navigation, UX interface design Functional description: Application for mobile (rugged tablets) with Windows 8.1/Windows 10 OS. Fullscreen application for remote service/support workers. Data for application can be fetch via online REST/protobuf connection or synchronized for offline work with the same connection and permament local data store (H2 DB). Operator can identify selected physical object by barcode/rfid (HF mifare) scanning. After reading data, application displays data about the selected object and can perform basic tasks. Stories: - application skeleton - skeleton, startup menu, fullscrenn mode, enlarged UI controls for hand use - exchange of data with server for online use - http/REST server communication and exchage information via protobuf messages - exchange of data for offline use - http/REST server communication and exchange information, store in local database. New database for each sync (does not have to resolve sync issues) - barcode identifier read - read of barcode identifier. Will be provided with libraries for reading barcode for a given hardware. - rfid identifier read - read of rfid tag. Will be provided with libraries for reading rfid tags for a given hardware. - product view (properties, tree structure, child element data, element parameters, files, service issues) - product view and its propertie (up to 30 parameters). Browsing product structure (element tree), element properties (up to 30 parameters), file list attached to product, service issues connected to product. - documentation browse - each product can have its documentation structure (object tree with connection to files-and-pages). Ability to browse structure, get file from server and display it using external application (adobe pdf etc.) Expected artifacts: - source code in Bitbucket mercurial repository - unit/integration tests for main controllers (business logic) - work on shared Jira instance with constant log of work
  • Number of freelancers needed: 2
Skills: Atlassian JIRA
Fixed-Price - Intermediate ($$) - Est. Budget: $50 - Posted
I am looking for some one to help me upgrade jira from 6.1 to 7, you must have previous system administration experience with jira upgrade
Skills: Atlassian JIRA Ubuntu
Fixed-Price - Intermediate ($$) - Est. Budget: $100 - Posted
Hi, I am running website for Software testing peoples to understand the basic concepts of Software Testing. We keep them updating with latest and fresh Software Testing knowledge. I am looking for person who can write tutorial series on "JIRA Software - Issue & Project Tracking Software". I want Jira tutorial series of 10-15 articles. Guidelines to submit the articles: Article should be original and must not be published anywhere else. Article should not be ripped-off from other web-site Article should be informative and share your unique expertise. Article must not be advertisement, press release, promotional offer or included any affiliate links. Article should be in English, spelling, grammar, punctuation, capitalization and sentence structure. And article must be unique, not copied from internet and atleast 1200 words long. I will pay you $6 / per article. Thanks, Kanif
Skills: Atlassian JIRA Software QA Testing Software Testing
Looking for the Team App?
Download the New Upwork Team App
Fixed Price Budget - ${{ job.amount.amount | number:0 }} to ${{ job.maxAmount.amount | number:0 }} Fixed-Price - Est. Budget: ${{ job.amount.amount | number:0 }} Open to Suggestion Hourly - Est. Time: {{ [job.duration, job.engagement].join(', ') }} - Posted
Skills: {{ skill.prettyName }}
Looking for the Team App?
Download the New Upwork Team App