What is the data model for an issue in JIRA for software projects? Is the hierarchy as follows - project->epics->stories->subtasks?
I want to create a Project management board with multiple stages . In this project, you can proceed to the next stage on only completing the earlier stages.
I wanted to create a 2-level hierarchy of workflows where the epics are in one workflow and the stories have their own workflow. Hence, there will be two boards
one showing the status of the epics in their workflow and
another
showing the status of the stories/tasks in their workflow
Is it possible to customize JIRA to allow this type of functionality?
The nice thing about JIRA boards is that they are simply views on issues. This means you can define what shows up on boards using JQL.
As an example, you could have a workflow for epics and then a board to show this workflow using a JQL that is something like this:
project = "myproject" and type = epic
Then you define a different workflow for your stories and show them on a different board using a JQL like this:
project = "myproject" and type = story
This means that even though the epics and stories both exist in the same project they can still be shown on different boards and with different workflows.
Related
We are using GitLab internally in my company, but I'm pretty new to this tool. We are only a few sprints into a new project, but have started arranging the backlog into epics and issues. I would now like to re-organize some of the epics and at least one needs to be a child of another epic. Both the (potential) child epic and the (potential) parent epic have issues of their own. I can create a new epic as a child, but want to just change an existing one.
In the Epic view, on the right hand side menu, there is an entry that says "Ancestors" but it isn't editable. Is there a different way to re-organize the epics into a hierarchy?
I want to start a project in JEE and I need to confirm about my class diagram. I need to know if the methods used are correct and if the composition I used is correct or not.
This is my class diagram:
The project is about an online sales store, that wants to set up a management tool to sell products, and to manage its products. This tool must include the following features:
Identification module: identification of clients, managers, supervisors
Sales module: make purchases for users
Product Management Module: Adding / Deleting Products
Statistical module: visualization of sales statistics
Functional Specifications
It is necessary to act on the application, to connect to the application with a user ID and password. To facilitate its use and in order to avoid any mishandling thereafter, here is the solution:
User Profile:
The user will be able to visualize the products sold by My Online Races. The user can place an order, provided that he has registered with the site My Online Races.
Manager profile:
The manager will be able to manage the products:
Add / Edit / Delete Products
Add / Edit / Delete category
These data insertions can be made using CSV or XML files, but also through various forms on the website.
The manager will be able to view the sales statistics.
Supervisor Profile:
The supervisor can add managers whose roles are specified above.
The supervisor will be able to view the sales statistics.
The supervisor will be able to view all the actions performed by the managers, a sort of audit trail.
Well I wish to know already if you have remarks about my design. As well as I have a confusion for several methods, for example adding, modifying and deleting a product. Should I put them in the manager or product class? Is the composition I put correct or should I remove it?
Quick review of the diagram and advices
First some minor remarks about class naming: Ordered should be called Order.
The composition between Article and Order is just wrong (not from a formal view, but from the meaning it conveys). Use a normal one-to-many association: it would reflect much better the real nature of the relation between the two classes. Please take into account that a new article may exist without having been ordered, so it shoud be 0..* instead of 1..*
+belongs and +do in the middle of an association are syntactically incorect. You should use a plain triangle instead (or nothing at all). The triangle should be oriented in the reading direction Person do |> Order and Article belongs to |> Category
The methods seem ok. You do not need to add a suffix.
How shall objects be managed (created/updated/deleted) ?
A more advanced concern is not about the diagram but about how you want to organise persistence (i.e. database storage):
do you really want the object to be an active record, that is an object that adds, updates and deletes itself (to the database) ? It's simple to set up, works well, but makes the class dependent on the underlying database implementation and thus makes maintenance more difficult;
or wouldn't it be better to use a repository for each object ? In this case the repository acts as a collection that manages all the database operations. The domain object (Article, order, User, ...) then have nothing to know about the database, wich leads to more maintainable code.
But this is a broader architectural question. If it's just for a first experimental project with JEE, you can very well use the active records. It's simpler to set up. Be sure however in this case to disambiguate the Add/Update/Delete on Person, since it currently may give the impression that any person can add anyone.
Improvement of the model
A final remark, again not about the diagram itself, is about the domain. Your model considers that an Order is about a single Article.
In reality however, orders are in general about one or several articles: if this would also be the case here, your Order would become an OrderItem and the real Order would be inserted between Person and OrderItem. You could then make the relation between Order and OrderItem a composition (i.e: OrderItem is owned by Order, which has responsibility for creating its items, and the items have no sense without the related order).
I have a relationship entity Fixture_In_Series which holds a relationship between FIXTURE and SERIES entity. Whenever any new fixture is associated/linked to a series a new record is generated in fixture_in_series.
I want my custom built Workflow Activity to fire whenever a new Fixture is associated to a Series and then it will do a job.
I can see Fixture and Series entity in the list when creating a new process but obviously Fixture_In_Series is not there as it is a relationship only.
Thanks for any suggestions.
I believe associate event is not possible to attach.
So i suggest you to use the OnUpdate\OnCreate Entity event and check if the lookup field Fixture has been filled.
From what you are saying it sounds like you are using a native many to many relationship between Fixture and Series. These entities cannot trigger workflows.
Two options that I see. Change your workflow to a plug-in and trigger it on the associate event.
Or, re-create your relationship as a custom many to many relationship. This involves you creating the intersection entity yourself, then you can trigger workflows on the update/create of the records in the intersection entity.
I want to create a class diagram UML for a part or bundle of my wbesite. This part contains three sub-parts :
Job : I want to show a list of jobs by date (title, date of job, location, deadline)
When I click on a job in list, I hope to have details of the job (title, description...)
Administration of list of jobs (delete, create, edit...)
I can imagine the template of view to create it but I hope to create a class diagram UML for Business Rules (class abstract,method,object...) to use after I create my code.
I'm not very professional in UML. Can someone give me an exepmle of graph or schema to create it, a prediction for method and object to use it in template.
Here is an example from some of my old college coursework. It may be of some use. Sorry if I can't help you further as I too am starting out professionally.
Note: Due to low reputation I can't post images so i have added the links accordingly.
I have this assignment I'm working and I am stuck in a recursive relationship, following is part of the case scenario that I am currently modelling;
Now, from the first Three paragraphs i have deducted the following business rules;
Employee is allocated ONE branch and a branch employs ONE or MANY employees
Each branch is designated ONE manager and ONE assistant manager
Employee is managed by ONE manager and supervised by ONE assistant manager
Employee submits ZERO, ONE or MANY previous employment records, a instance of a record is associated to ONE employee only
Employee is assigned ONE job position only, a job position can be assigned to ONE or MANY employees
(note: I have assumed in rule n.2 that a branch is also designated an assistant manager)
And now this is the ERD diagram for the above rules;
So from the scenario, the assistant manager only supervises the staff, but it does not say that it has any relationship with the branch entity, however i assumed that a branch should have a relationship with the the manager and the assistant manager, but i am a bit confused so i havent added it yet to the erd diagram. Can you guys help me out?
Firstly it appears you seem to be drawing a UML Domain model not a ER diagram. These are not the same thing. You've identified an employee but seem to be trying to use it polymophically for all things. This premature optimisation (and for re-use), when you should be following the rules of normalisation of entity relationships. Take a step back, create tables for manager, assistent manager and employee. Add the fields to those, THEN try to normalise.